Cavemanon/SnootGame
25
Fork 18
Code Issues 4 Pull Requests 1 Actions Projects Releases 10 Wiki Activity

CI/CD #222

New Issue
Closed
opened 2023-05-07 05:13:18 +00:00 by MichaelYick · 2 comments
MichaelYick commented 2023-05-07 05:13:18 +00:00
Owner
Copy Link

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.

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.
MichaelYick added the
enhancement
Low Priority
 labels 2023-05-07 05:13:19 +00:00
MichaelYick self-assigned this 2023-05-07 05:13:19 +00:00
san7890 commented 2023-05-07 05:58:16 +00:00
Contributor
Copy Link

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?

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?
MichaelYick commented 2023-05-07 06:12:22 +00:00
Author
Owner
Copy Link

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.

> 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.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
Critical Priority
Absolutely urgent issues that must be delt with before others can even be considered.
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
High Priority
Bugs that cause crashes, major story errors, or other massively negative issues. Features that are a must-have inclusion or else the game won't be as good.
Low Priority
Minor or easy to miss errors. Features that'd be nice, but can be done with out.
Medium Priority
Errors that stick out, but aren't fatal to gameplay. Features that are in decent demand or would improve gameplay by a signifigant amount
Meta
for all the other fun stuff about the project thats not code
needs more info
Something is wrong
question
refactor
Cleaning up the cruft
wontfix
This won't be fixed
bug
Something is not working
Critical Priority
Absolutely urgent issues that must be delt with before others can even be considered.
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
High Priority
Bugs that cause crashes, major story errors, or other massively negative issues. Features that are a must-have inclusion or else the game won't be as good.
invalid
Something is wrong
Low Priority
Minor or easy to miss errors. Features that'd be nice, but can be done with out.
Medium Priority
Errors that stick out, but aren't fatal to gameplay. Features that are in decent demand or would improve gameplay by a signifigant amount
Meta
for all the other fun stuff about the project thats not code
question
More information is needed
wontfix
This won't be fixed
No Label
enhancement
Low Priority
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Cereal Jatmoz Jingo Jluminate Legalo Map MapAnon MichaelYick Mod Nerd Nio nutbuster ReleaseSmith Sl1 TheNerd writerdev
No Assignees MichaelYick
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Cavemanon/SnootGame#222
No description provided.
Delete Branch "%!s()"

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?