ENH: Add a script to update the remote module commit hashes#632
Conversation
|
As discussed some time ago by mail. A few comments:
|
thewtex
left a comment
There was a problem hiding this comment.
Super cool @jhlegarreta! 🥇
A few suggestions inline.
|
This also provides a dependency-free way to get the latest commit on GitHub: https://stackoverflow.com/questions/15677439/command-to-get-latest-git-commit-hash-from-a-branch |
dzenanz
left a comment
There was a problem hiding this comment.
Excellent that you got to this! Matt has already provided excellent feedback.
b68921c to
e9d1318
Compare
Nice ! Done in e9d1318 and a variable name error fixed ! Thanks both. |
e9d1318 to
509207d
Compare
Add a script to update the remote module commit hashes. Update the `Release.md` guide to add the remote module update step prior to a release.
509207d to
8fdb454
Compare
|
|
||
| 1. Update the ITK tag used in the `azure-pipelines.yml` CI configuration and the | ||
| `setup.py` Python setup files using the [](https://github.com/InsightSoftwareConsortium/ITK/tree/master/Utilities/Maintenance/) | ||
| script. This will involve merging a new pull request to each remote module |
There was a problem hiding this comment.
Used the term involve because the commit/PR is not yet automatic.
Eventually a Documentation/Maintenance/UpdatingRemotes.md could be created, much like it exists for the ThirdParty modules, and that document could be linked from here. But that is left for an eventual future PR.
|
Added a note in the |
thewtex
left a comment
There was a problem hiding this comment.
Thanks @jhlegarreta ! This will be very helpful.
|
This is great @jhlegarreta! |
…RemotesHashUpdateScript ENH: Add a script to update the remote module commit hashes
Add a script to update the remote module commit hashes.
Update the
Release.mdguide to add the remote module update step priorto a release.