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

Enable markdown link checker #26

Closed
Disper opened this issue Sep 15, 2023 · 3 comments · Fixed by #56
Closed

Enable markdown link checker #26

Disper opened this issue Sep 15, 2023 · 3 comments · Fixed by #56
Assignees
@grego952
Labels
area/application-connector Issues or PRs related to application connectivity area/documentation Issues or PRs related to documentation kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Disper
Copy link
Member

Disper commented Sep 15, 2023 •
edited
Loading

Description

Configure a markdown link checker that will ensure that links we use in our *.MD files are valid.

Reasons

  • Documentation consistency
  • Good developer experience

Attachments

/area documentation
/area application-connector
/kind feature
@kyma-bot kyma-bot added area/documentation Issues or PRs related to documentation kind/feature Categorizes issue or PR as related to a new feature. labels Sep 15, 2023
@kyma-project kyma-project deleted a comment from kyma-bot Sep 15, 2023
@Disper Disper added the area/application-connector Issues or PRs related to application connectivity label Sep 15, 2023
This was referenced Sep 15, 2023
Closed
Closed
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 14, 2023
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

@kyma-bot
Copy link
Contributor

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Disper Disper removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 21, 2023
@Disper Disper reopened this Nov 21, 2023
@grego952 grego952 self-assigned this Nov 30, 2023
@grego952 grego952 mentioned this issue Nov 30, 2023
Merged
kyma-bot added a commit that referenced this issue Dec 5, 2023
@kyma-bot
Add link checker to compass manager (#56)
8978500 
<!-- Thank you for your contribution. Before you submit the pull
request:
1. Follow contributing guidelines, templates, the recommended Git
workflow, and any related documentation.
2. Read and submit the required Contributor Licence Agreements
(https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md#agreements-and-licenses).
3. Test your changes and attach their results to the pull request.
4. Update the relevant documentation.

If the pull request requires a decision, follow the [decision-making
process](https://github.com/kyma-project/community/blob/main/governance.md)
and replace the PR template with the [decision record
template](https://github.com/kyma-project/community/blob/main/.github/ISSUE_TEMPLATE/decision-record.md).
-->

**Description**

Changes proposed in this pull request:

- Add link checker to compass manager

**Related issue(s)**
Fixes #26 
<!-- If you refer to a particular issue, provide its number. For
example, `Resolves #123`, `Fixes #43`, or `See also #33`. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@grego952 grego952

Labels
area/application-connector Issues or PRs related to application connectivity area/documentation Issues or PRs related to documentation kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add link checker to compass manager grego952/compass-manager
3 participants
@Disper @kyma-bot @grego952