Conversation
- Remove build artifacts from version control - Add .gitignore to prevent future build artifacts - Clean up REUSE.toml to remove NOASSERTION entries Build artifacts will be generated during CI/CD and available as downloadable artifacts from GitHub Actions.
This file contains hidden or 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
1 participant
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.
While inspecting the actions that builds the artifacts.
https://github.com/vejeta/conquerv5/actions/
Notice that the APK was built, but the verification steps were failing.
This is to fix the APK validation step.
Additionally, there was some warnings about unrecognized licenses, so we perform a consolidation of the LICENSE files for better parsing of tools that check legal compliance.