Disable CodeQL and cppcheck workflow runs for cFS Bundle
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.
The CodeQL and static analysis workflows should are already checked at the submodule level.
Furthermore, the github security scanning dashboard doesn't work well with SARIF files that point to files from submodule so running the CodeQL workflow with each commit or PR doesn't help.
Describe the solution you'd like
Remove pull request and push triggers from CodeQL and cppcheck workflows. Keep them as "workflow dispatch" in case someone wants to run the analysis on the bundle.
Describe alternatives you've considered
a) Keep as is.
b) Completely remove workflows
Additional context
None
Requester Info
Gerardo E. Cruz-Ortiz, NASA
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
Locate the CodeQL and cppcheck workflow definitions and inspect their current push and pull_request triggers. Retain workflow_dispatch as the only trigger for each workflow, then verify the workflow configuration and ensure no pull request or push trigger remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100