Bug(CI): CI duplication and messiness
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 11
Description
Describe the bug
I'm seeing duplicates in CI after: https://github.com/python/pythondotorg/pull/2852, specifically in https://github.com/python/pythondotorg/pull/2868's lint CI runs (runs 2x).
[Check collectstatic / collectstatic (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335873/job/60278606528?pr=2868)Successful in 36s
[CI / migrations (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335870/job/60278606563?pr=2868)
CI / migrations (pull_request)Successful in 1m
[CI / test (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335870/job/60278606515?pr=2868)
CI / test (pull_request)Successful in 4m
Required
[docs/readthedocs.org:pythondotorg](https://pythondotorg--2868.org.readthedocs.build/)
docs/readthedocs.org:pythondotorg — Read the Docs build succeeded!
[Lint / lint (pull_request)](https://github.com/python/pythondotorg/actions/runs/20972335874/job/60278606581?pr=2868)
Lint / lint (pull_request)Successful in 16s
[Lint / lint (push)](https://github.com/python/pythondotorg/actions/runs/20972309130/job/60278514578?pr=2868)
Lint / lint (push)Successful in 14s
Terraform Cloud/psf/pythondotorg-infra
Terraform Cloud/psf/pythondotorg-infra
I don't like this and it's confusing to me why we have this problem in the first place because none of my other projects have ever had this weird double CI run thing.
To Reproduce
.
Expected behavior
No duplicates
URL to the issue
No response
Screenshots
Browsers
Other
Operating System
Other
Browser Version
No response
Relevant log output
Additional context
No response
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
Review the CI changes introduced by pull request #2852 and compare the pull request #2868 checks, especially the duplicated Lint runs and Terraform Cloud entries. Confirm which workflows are triggering each check and consider the issue complete when pull requests produce no duplicate CI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, terraform
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100