This was modeled after MyLA. There aren't branches here like there is in MyLA, just master.
I tested the build process for master and that creates that package fine. I've also tested the tags.
Testing
Once this is merged it will be straightforward to test.
If you'd like to checkout this branch and test it on your repository before merging, you'd have to update the value of tl-its-umich-edu to your user name and merge or cherry-pick this change to your repositories master for it to trigger a build. It will not do anything in this branch.
Afterward you'd need to do a hard reset to your fork's master branch to clean all of this up.
Assuming your remote is origin and tl-its-umich-edu is upstream for instance for me I have this
This was modeled after MyLA. There aren't branches here like there is in MyLA, just master.
I tested the build process for master and that creates that package fine. I've also tested the tags.
Testing
Once this is merged it will be straightforward to test.
If you'd like to checkout this branch and test it on your repository before merging, you'd have to update the value of
tl-its-umich-edu
to your user name and merge or cherry-pick this change to your repositoriesmaster
for it to trigger a build. It will not do anything in this branch.Afterward you'd need to do a hard reset to your fork's master branch to clean all of this up.
Assuming your remote is
origin
and tl-its-umich-edu isupstream
for instance for me I have thisEnsure that your master from upstream is updated.
Then you'd run
git reset --hard upstream/master
Then push it
git push origin master --force-with-lease
You can't force push onto the wrong repository, it will give you an error.