I think a move to Git is a great idea. I found SVN a little quirky (but then I
learned on Git, so maybe I'm just not used to it). Either way, you have my
vote for Git.
On Saturday, July 13, 2019 12:07:11 PM Jonathan Blake wrote:
Hello all,
I'm (seriously) considering whether we should migrate from Subversion to
Git for our source control. Your thoughts?
This seems like a good intro to working with Git
<https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d
4ac6?gi=c3f2fb5604ab> .
To verify that it's even feasible, I've converted the repository and set up
public read-only access over the web. I've also disabled SVN commits for
now to avoid divergent code bases.
https://git.projectaon.org/
Anyone can clone the repo over HTTPS, but in order to commit changes, you
need to clone over SSH using your web server account, replacing my username
(jonathan) with yours.
git clone ssh://jonathan@xxxxxxxxxxxxxx/~aongit/repos/project-aon.git
When migrating, I used everyone's @projectaon.org email addresses to avoid
publicly listing private addresses. You can still get spam because the mail
is forwarded, but we can adjust the forwarding if that becomes an issue.
cd project-aon
git config --local user.name "Your Name"
git config --local user.email "your.name@xxxxxxxxxxxxxx"
Please avoid working directly in the master branch. Other than that, I'm
open to suggestions about branching strategies, the simpler the better.
git checkout develop
I've added everyone who has committed in the past to the list of people who
will be notified by email when things are pushed. Let me know if you don't
want to be notified.
Anything else I should do? Is this a bad idea? :)
--
Jon