InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Markdownlint Action is running twice
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
I noticed that the markdownlint GitHub Action that we have is running twice on the same PR.
It is mostly a cosmetic problem and it also might be a bit confusing for people.
I know that we could prevent it by limiting the action workflow execution to pushes to master like in this GHA configuration. However that seems to have other undesirable consequences.
I wonder if there is some way to do this?
Example:
See the bottom of https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/261/
Screenshot:
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
Inspect the GitHub Actions workflow configuration and compare it with the linked .github/workflows/lint-patterns.yml example, then review the duplicate runs shown on pull request #261. Done means markdownlint runs once per pull request without losing the desired workflow behavior on pushes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, markdown
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100