CI/CD #222
Labels
No Label
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
Low Priority
Medium Priority
Meta
needs more info
question
refactor
wontfix
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
invalid
Low Priority
Medium Priority
Meta
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Cavemanon/SnootGame#222
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Might be wise to get woodpecker CI or gitea's new CI system set up in case we ever make some releases of snoot game again.
Just spitballing the concept, but how would we even measure success/failure in something like unit testing every ending to ensure it still works as desired? Or: would this just be limited to linting for common mistakes?
Cavemanon's other projects, Wani and Exit, currently have a CI/CD system using Woodpecker CI. The current scope of the system in these projects is compiling automation, build archival, and testing if PRs have big errors or not. No real unit testing currently, and given how small snoot game is as a project, I believe that it'd merely be a nicety to have, not a necessity.