Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore] Don't check changelog links in CI #3424

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

swiatekm
Copy link
Contributor

@swiatekm swiatekm commented Nov 6, 2024

Looking at some recent failures of the changelog workflow on PRs: https://github.com/open-telemetry/opentelemetry-operator/actions/workflows/changelog.yaml, I noticed the link check doesn't do anything useful. The changelog tool's preview command actually outputs the new changelog segment to stderr (and not stdout as the docs claim), so we're running markdown-link-check on some random chloggen output.

Furthermore, it doesn't even make sense to check this - what we should do instead is check changelog links during releases, or check links in all of our docs at different points. For now, I'm removing the blocker.

@swiatekm swiatekm requested a review from a team as a code owner November 6, 2024 09:01
@swiatekm swiatekm marked this pull request as draft November 6, 2024 09:30
@swiatekm swiatekm force-pushed the chore/changellg-check-links branch from d4e4b91 to a06b879 Compare November 6, 2024 10:28
@swiatekm swiatekm changed the title [chore] Check links in CHANGELOG when updating it [chore] Don't check changelog links in CI Nov 6, 2024
@swiatekm swiatekm marked this pull request as ready for review November 6, 2024 10:29
@swiatekm swiatekm mentioned this pull request Nov 6, 2024
@swiatekm swiatekm merged commit bc45d63 into open-telemetry:main Nov 6, 2024
38 checks passed
@swiatekm swiatekm deleted the chore/changellg-check-links branch November 12, 2024 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants