We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce git-merge command that would complement git-checkout command.
git-merge
git-checkout
Its purpose is to merge a set of PRs to master and possibly to push
master
Example workflow:
The integrator checks a set of PR:
$ reana-dev git-checkout --fetch \ -b r-w-controller 401 \ -b r-j-controller 302 \
When everything is working, the integrator would like to merge some of them to master:
$ reana-dev git-merge -b r-w-controller 401 -b r-j-controller 302 [--push]
This command should do, for each given repo:
pr-401
upstream/pr/401
git merge --ff-only upstream/pr/401
--push
upstream
origin
git-push
For example, I have been using the following alias:
merge-push-delete-pr = !sh -c 'git fetch upstream && git checkout master && git merge --ff-only upstream/master && git merge --ff-only upstream/pr/$1 && git branch -d pr-$1 && git push upstream master && git push origin master' -
The command would do something similar, but for a set of REANA components associated to a PR group.
Note: we could use simple git commands for now and investigate moving to gh command later (starting from git-fork and friends).
gh
git-fork
The text was updated successfully, but these errors were encountered:
cli: add git-merge command
7e22a2c
closes reanahub#362
d6eb41d
5d3fa9c
7dffa6d
mvidalgarcia
Successfully merging a pull request may close this issue.
Introduce
git-merge
command that would complementgit-checkout
command.Its purpose is to merge a set of PRs to
master
and possibly to pushExample workflow:
The integrator checks a set of PR:
When everything is working, the integrator would like to merge some of them to master:
$ reana-dev git-merge -b r-w-controller 401 -b r-j-controller 302 [--push]
This command should do, for each given repo:
pr-401
branch is identical toupstream/pr/401
to prevent errors;git merge --ff-only upstream/pr/401
tomaster
pr-401
--push
argument is used, the newmaster
branch should be pushed toupstream
andorigin
;git-push
command which could be also amended for that effect (to add an option where to push,origin
orupstream
)For example, I have been using the following alias:
The command would do something similar, but for a set of REANA components associated to a PR group.
Note: we could use simple git commands for now and investigate moving to
gh
command later (starting fromgit-fork
and friends).The text was updated successfully, but these errors were encountered: