Auto-versioning #20
Merged
Auto-versioning #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create a metadata file (project.toml) that mimics relevant information based on PEP 621 for python project metadata. Dropped the `py` in the file name to indicate that this is not a python project - don't believe there is a standard for GHA. This file was created with intentions to be used for auto versioning. Note, updating of versions within workflows and actions is still a manual process. Part of this is to ensure the correct items are updated with the correct context.
Add example of .secrets file to use for local testing with nektos/act. Also update README with information about local testing.
Change from dash (-) to underscore (_) to conform to Github actions / env syntax.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds functionality for auto-versioning of this repository by using the workflows that have been configured. Note, versions within the workflow still need to be manually updated. The purposes of this to easily update the versions, ultimately for release tags.