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
So say you do ./release-gap-package 1.2.3
./release-gap-package 1.2.3
Then it could update PackageInfo.g and set that version in there, and the current date, and commit that. It'd possible also update CHANGES.md (see also issue #19, and my limited implementation in https://github.com/oscar-system/GAP.jl/blob/master/etc/update_version.sh)
PackageInfo.g
CHANGES.md
Of course ideally it should also verify the package version actually increases.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
So say you do
./release-gap-package 1.2.3
Then it could update
PackageInfo.g
and set that version in there, and the current date, and commit that. It'd possible also updateCHANGES.md
(see also issue #19, and my limited implementation in https://github.com/oscar-system/GAP.jl/blob/master/etc/update_version.sh)Of course ideally it should also verify the package version actually increases.
The text was updated successfully, but these errors were encountered: