CircleCI do not run CI when changing documentation or markdown files
Open
Nobody has claimed this yet.
Category: Build System
Feature
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Similar to what was done for Cirrus with https://github.com/php/php-src/pull/16203
Just saw that we ran CI when pushing https://github.com/php/php-src/pull/16415
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
Start by reviewing the CircleCI configuration and compare it with the change described in Cirrus PR 16203. Check how documentation or Markdown-only changes are currently handled, then verify that such changes no longer trigger CircleCI while code changes still do.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100