Checkouts stale following changes to .gitattributes
Open
Nobody has claimed this yet.
docs
infra
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44779 |
|---|---|
| Nosy | @jaraco, @jkloth, @eamanu |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2021-07-30.14:21:05.787>
labels = ['docs']
title = 'Checkouts stale following changes to .gitattributes'
updated_at = <Date 2021-07-31.13:27:52.992>
user = 'https://github.com/jaraco'
bugs.python.org fields:
activity = <Date 2021-07-31.13:27:52.992>
actor = 'eamanu'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-07-30.14:21:05.787>
creator = 'jaraco'
dependencies = []
files = []
hgrepos = []
issue_num = 44779
keywords = ['patch']
message_count = 1.0
messages = ['398552']
nosy_count = 4.0
nosy_names = ['jaraco', 'jkloth', 'docs@python', 'eamanu']
pr_nums = ['27436']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue44779'
versions = []
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 .gitattributes changes and PR #27436, which is listed in the issue history. Check how the affected checkout becomes stale after those changes and use the existing PR context to determine the intended fix. Done means checkouts remain current after .gitattributes changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100