summaryrefslogtreecommitdiffstats
path: root/gitautodeploy/parsers/common.py
Commit message (Collapse)AuthorAgeFilesLines
* RefactoringHEADorigin/masterorigin/HEADmasterOliver Poignant2017-01-081-30/+0
|
* Refactoring and preparations for JSON APIOliver Poignant2016-12-121-2/+5
|
* Verify secret token in GitLab requestsOliver Poignant2016-12-091-0/+3
|
* Modifying config option name and adding docsOliver Poignant2016-11-291-1/+1
|
* Allow more than one GitHub repo from the same userHenk Hesselink2016-11-201-2/+2
| | | | | | | | | | | | | | | | | | | | | GitHub does not allow the same SSH key to be used for multiple repositories on the same server belonging to the same user, see: http://snipe.net/2013/04/multiple-github-deploy-keys-single-server The fix there doesn't work because the "url" field is used both to get the repo and to identify it when a push comes in. Using a local SSH name for the repo works for getting the repo but then the name in the push doesn't match. This patch adds a 'repo' option that that can be set to the name of the repo as given in the push. If 'repo' is not set the behaviour is unchanged. Example: "url": "git@repo-a-shortname/somerepo.git" "repo": "git@github.com/somerepo.git"
* Store parent in common.pyOliver Poignant2016-03-061-0/+24