...
Where Y.Y.Y is the new version number and the name of our branch.
In the branching step, all the components that are needed to be changed will have been cloned in the destination folder so finding the requirements.txt files to be changed will be easy.
You will need to commit each repo after the file has been updated.
...
The command
This can be done with the command.
| Code Block |
|---|
rr_git.py --action update --branch Y.Y.Y --destination C:/Mywork/UKRR/Y.Y.Y --message "Update requirements.txt"Should do this automatically however it currently doesn't |
| Note | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
At the moment the above command willl only work if there is isn't an existing branch tag in the URL (leading to duplication). This needs the URLs in the URLs. If there is the Search/Replace will duplicate the tags and things will break. There shouldn't be any tags in the URls if the Deployment instructions have been followed correctly so you should be able to use the command.
|
Updating Version Numbers
...