Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Markdownlint Action is running twice

Open
#267 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, markdown
Domain
ci-cd

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.

Description

:gear: Type - Meta

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:

markdownlint-running-twice

Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InnerSourceCommons/InnerSourcePatterns

All issues in InnerSourceCommons/InnerSourcePatterns

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.