REQUEST: Repository maintenance on opentelemetry-collector-releases
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- devops
Research direction
Start with the repository configuration guidelines and issue #1088, then inspect the existing cleanup workflow described there. Confirm how the organization’s immutable tag rule applies to this repository and whether a tag-pattern exception is supported. Done means nightly release tags and resulting container image tags can be cleaned up without violating the organization policy.
Written by the indexing model from the issue text.
Description
Affected Repository
https://github.com/open-telemetry/opentelemetry-collector-releases
Requested changes
Allow exception for deleting tags with specific pattern in repo
In the otel-collector-releases repo, we do nightly releases to make sure that the release works end to end and that new changes on the collector source code repos still work when it comes to the release. This produces 3 tags every night.
Purpose
Until now, those tags were never cleaned up and pollute the repo quite a bit. As part of https://github.com/open-telemetry/opentelemetry-collector-releases/issues/1088, I wrote a github workflow to clean up those tags together with the resulting container image tags, but ran into troubles because of immutable github tag rules.
Is there any way we can add an exception to that org-level rule for our repo? The only alternative I see would be to have some maintainer-level bot user with a token which would then be able to use the maintainer bypass in the rule.
Expected Duration
permanently
Repository Maintainers
- @open-telemetry/collector-releases-maintainers
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 326
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from open-telemetry/community
-
area/github-membership
Difficulty 1/5 Under an hour Newbie friendliness 1/100
open-telemetry/community#3847 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
open-telemetry/community#3846 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
open-telemetry/community#3844 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
open-telemetry/community#3823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
open-telemetry/community#3821 · 3 comments ·
Maintainers usually reply within 1 day
All issues in open-telemetry/community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day