I do use branches in my personal projects, though not as much. In general, if I have some CI checks that can run on my code, I will be using a branch and wait for the CI to run before merging something. If I do something that only requires one commit and I do not have any CI, and I feel confident enough, I will commit to main. If I do something that is linked to an issue on Gitea or another git web UI, or that I am not really sure of, or that is way too long to fit in one commit, it all goes in a branch.
I do not really commit that often, because I forget to commit, I do not really like making WIP commits or committing broken code, and my projects are small enough that I barely use the Git history or need to look up exactly why I did something. When I need to see why I did something, I will be reading my code comments, my notebooks, or the comments I write on git web UIs.
I do not really commit that often, because I forget to commit, I do not really like making WIP commits or committing broken code, and my projects are small enough that I barely use the Git history or need to look up exactly why I did something. When I need to see why I did something, I will be reading my code comments, my notebooks, or the comments I write on git web UIs.
This is probably a good idea I need to do more, lol.
I’ve had a couple reports of this now and I haven’t been able to reproduce… source code is here if anyone wants to have a stab. I can try to dig up some logs too if that helps.
The original article got deleted; see the author’s follow-up and the official change proposal instead
thanks for the updated links. :)
I do use branches in my personal projects, though not as much. In general, if I have some CI checks that can run on my code, I will be using a branch and wait for the CI to run before merging something. If I do something that only requires one commit and I do not have any CI, and I feel confident enough, I will commit to main. If I do something that is linked to an issue on Gitea or another git web UI, or that I am not really sure of, or that is way too long to fit in one commit, it all goes in a branch.
I do not really commit that often, because I forget to commit, I do not really like making WIP commits or committing broken code, and my projects are small enough that I barely use the Git history or need to look up exactly why I did something. When I need to see why I did something, I will be reading my code comments, my notebooks, or the comments I write on git web UIs.
This is probably a good idea I need to do more, lol.
SOFA
SOFA?
https://tilde.town/~dozens/sofa/
Thanks:)
I tried submitting a post today and this is what happens in Chrome: https://ttm.sh/EUM.png
I had some similar issues recently and managed to post after a few days for absolutely no reason!
i had the same issue, but it worked fine when i posted a different URL, not sure why
I’ve had a couple reports of this now and I haven’t been able to reproduce… source code is here if anyone wants to have a stab. I can try to dig up some logs too if that helps.
Perfect.
Probably pulled directly from one of these manpages :)
Doesn’t seem to work in FF nightly.
Same with FF Developer Edition 73.0b7 :/