Check Tokens Consistency #63
Merged
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
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.
Issue Add Github Actions for checking tokens.txt and reader constants consistency #60
The corresponding workflow action has been tested in PR #62. This approach aims to prevent test commits and their reverts from cluttering the change history of the token files.
Therefore, the workflow should be validated in PR #62 and merged through this PR. It is important that this PR does not include any test commits related to the token files.
Potential Dependency: Protein function prediction with GO - Part 2 #57
PR #57 introduces a new tokens file related to protein trigrams. We can incorporate this file into the workflow configuration once that PR has been merged.