nofusscomputing / nofusscomputing/action_docker
Add check for workflow already running with matching commit
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As this workflow can potentially overwrite the same actions if two workflows are running, i.e. push and tag. a check needs to be done to find the first workflow so that no additional rebuilding is done.
The check should cause the newest workflow to pause if the commit is the same and to wait for the first one to complete.
Details
A query to the API could be done and if the branch is regex match a tag and the current running job is on the same commit, then stop. this will then prevent an overwrite of build items that are not tagged.
So that the status of the branch job is not that of "reported" true/false. wait for the tagged job to finish and report it's status as the the same as the tagged job's run status.
Workflow
-
Wait
xperiod of time -
query endpoint using commit sha
-
workflow found with same commit and workflow job
CI-
current workflow not
git tag-
Found workflow that is git tag
-
post markdown status to workflow pointing to tagged branch
action: dtinth/markdown-report-action
-
stop workflow from continuing
-
-
-
Current workflow is
git tag- continue workflow
-
Links
Contributor guide
No contributing guide indexed for this repository
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
Start by inspecting the CI workflow and the workflow-runs API endpoint, using head_sha to find runs for the same commit and checking which run is tagged. Confirm how dtinth/markdown-report-action is used for status reporting. Done means a newer non-tag workflow waits when a tagged run for the commit exists and reports that run's final status.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100