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.

Sign up for GitHub

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

Jump to bottom

ci(lint): markdown link check as warning #468

Merged
merged 1 commit into from
Dec 11, 2024
Merged

ci(lint): markdown link check as warning #468

merged 1 commit into from
Dec 11, 2024

Conversation

AtomicFS
Copy link
Collaborator

  • downgrade failed markdown link checks from error to warning
  • this is because of frequent errors

@AtomicFS
ci(lint): markdown link check as warning
750ede7 
- downgrade failed markdown link checks from error to warning
- this is because of frequent errors

Signed-off-by: AtomicFS <[email protected]>
@AtomicFS AtomicFS requested a review from MDr164 as a code owner December 11, 2024 10:59
@github-actions github-actions bot added testing Testing related bugfix Bugfix / fix labels Dec 11, 2024
@AtomicFS AtomicFS enabled auto-merge December 11, 2024 10:59
MDr164
MDr164 approved these changes Dec 11, 2024
View reviewed changes
Copy link
Collaborator

@MDr164 MDr164 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a reasonable change, that lint check shouldn't block merging

@AtomicFS AtomicFS added this pull request to the merge queue Dec 11, 2024
Merged via the queue into main with commit 1b4c19e Dec 11, 2024
42 checks passed
@AtomicFS AtomicFS deleted the fix/markdown-link-check branch December 11, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MDr164 MDr164 MDr164 approved these changes

Assignees
No one assigned
Labels
bugfix Bugfix / fix testing Testing related
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@AtomicFS @MDr164