I should get more into it, but one thing I am always not sure about: How do you test them? Have them on a separate branch (or even repo) and then trigger them? That seems a bit restrictive
this post was submitted on 19 Jun 2023
3 points (80.0% liked)
DevOps
1690 readers
1 users here now
DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.
Rules:
- Posts must be relevant to DevOps
- No NSFW content
- No hate speech, bigotry, etc
- Try to keep discussions on topic
- No spam of tools/companies/advertisements
- It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
Yes, usually most things can be tested on a different branch and just set the workflow to trigger from the branch rather than main. There are some cases where this doesn't work great, however, like testing triggers for pull requests, since then you have to have a 2nd branch to PR to the test branch.
There is also nectos/act, although I don't personally use it, I have heard it helps with faster development of workflows (and saves cost if you are not self hosting runners).