Ensure Workflow Triggers are Consistent
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 391
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 19
Description
Checklist (Please check before submitting)
- I reviewed the Contributing Guide.
- I reviewed the cFS README.md file to see if the feature is in the major future work.
- I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.
Is your feature request related to a problem? Please describe.
There are MCDC and Build and Run workflows with schedules. Not all MCDC or Build and Run workflows have these schedules. For example, ci_lab Build and Run has a schedule, while LC does not.
Describe the solution you'd like
All internal and opensource workflows across the cFS repositories should have the same triggers.
Requester Info
Ariel Walker, MCSG TECH.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare .github/workflows/build-run-app-internal.yml in the ci_lab and LC repositories, starting with their workflow trigger sections and schedules. Then audit the MCDC and Build and Run workflows across the cFS repositories; done means the internal and open-source workflows use consistent triggers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100