IDK how you end up with so many repos that you need to clean them up. One good decision was to put all my Emacs Lisp programs under one repo. Melpa guys didn't like it because it messes with Melpa...
IDK how you end up with so many repos that you need to clean them up. One good decision was to put all my Emacs Lisp programs under one repo. Melpa guys didn't like it because it messes with Melpa Stable (which they recommend people shouldn't use, duh), but I'm happy I have one place all my public Elisp lies, and one Readme.org file to deal with issue tracking. The biggest thing there is ~1kloc anyways.
One thing I really dislike with Github is that it is based on the fork-edit-commit-PR workflow, which is totally an overkill. It is easier to just git clone something and send the output of git format-patch somehow. Every now and then I get a pull request, and IDK what to do about them. git am is not the most pleasant thing to use, but at least it has good, detailed docs (git-am(1)). Github hides all this behind a PR, and forces you to make a "fork", which is basically a clone/checkout of the repo made via a web interface. Then you need to clone that clone locally and then push/pull to it, and it is way harder to get rid of: on my computer, it is often cd co/External; rm -rf <repo>. And in most cases you don't need the full clone or even the git repo to submit a patch: just diff(1) and send. No need to make "single user organisations", just make directories.
IDK how you end up with so many repos that you need to clean them up. One good decision was to put all my Emacs Lisp programs under one repo. Melpa guys didn't like it because it messes with Melpa Stable (which they recommend people shouldn't use, duh), but I'm happy I have one place all my public Elisp lies, and one Readme.org file to deal with issue tracking. The biggest thing there is ~1kloc anyways.
One thing I really dislike with Github is that it is based on the fork-edit-commit-PR workflow, which is totally an overkill. It is easier to just
git clonesomething and send the output ofgit format-patchsomehow. Every now and then I get a pull request, and IDK what to do about them.git amis not the most pleasant thing to use, but at least it has good, detailed docs (git-am(1)). Github hides all this behind a PR, and forces you to make a "fork", which is basically a clone/checkout of the repo made via a web interface. Then you need to clone that clone locally and then push/pull to it, and it is way harder to get rid of: on my computer, it is oftencd co/External; rm -rf <repo>. And in most cases you don't need the full clone or even the git repo to submit a patch: justdiff(1)and send. No need to make "single user organisations", just make directories.This isn't really Bash, just a cURL command. It would work just fine in other shells, even Python and such if you reformat it.