To request an account join #agocontrol-devel on freenode and talk to one of the Core Developers. We'll add self-enrollment soon. If you had an account on the old git, you need to go here to reset your password via email (press "Email password reset link" - this is needed because the old apache md5 hash can't be used with the new system): http://agocontrol.com/account
Should your email be wrong (I've fetched them from the git commits) please contact hari on irc.
The repository runs on our local gitlab installation. You can access it here: http://git.agocontrol.com
Make sure to set your username and email:
git config --global user.email "firstname.lastname@example.org" git config --global user.name "Jim Smith"
git config --global push.default current
change branch to develop
cd agocontrol git checkout -b develop origin/develop
git status git add <path/file> git commit -m "<your comment>" git push
If you don't have rights to push to the main repo you can fork the project on Gitlab and issue a pull request. Make sure you have added your ssh key (see http://git.agocontrol.com/profile/keys for instructions). For example to clone your agocontrol / agocontrol file:
git clone email@example.com:<user>/agocontrol.git
Check your git config file so that it's using SSH. sudo nano .git/config
[remote "origin"] firstname.lastname@example.org:agocontrol/agocontrol.git
Wiki logins now work with the developer accounts: http://wiki.agocontrol.com
Buildbot is currently used to build packages on every commit. It runs on our builder system: http://builder.agocontrol.com:8010
This is not tied into the new authentication system yet.
Gitlab-CI runs here: http://gitlab-ci.agocontrol.com This has integration into Gitlab. The nice thing is that every commit will have a build status (success/pending/failed). The downside is that it is far not as flexible as Buildbot. So this will not replace buildbot but augment it for quick testing of change sets.
A test installation is set up and allows login with the developer account. Contact hari on irc for further details.
I'd propose to adopt the branching model explained here: http://nvie.com/posts/a-successful-git-branching-model/
Further discussion pending.