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

docs: Add all md files in root dir to linkchecker #1461

Closed
wants to merge 11 commits into from

Conversation

p-offtermatt
Copy link
Contributor

@p-offtermatt p-offtermatt commented Nov 30, 2023

Description

  • Fixes links that are currently broken
  • Enables the markdown checker on more files (all files in the repo root and in the docs/docs folder)

Closes: N/A


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct docs: prefix in the PR title
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • Confirmed the correct docs: prefix in the PR title
  • Confirmed all author checklist items have been addressed
  • Confirmed that this PR only changes documentation
  • Reviewed content for consistency
  • Reviewed content for spelling and grammar
  • Tested instructions (if applicable)
  • Checked that the documentation website can be built and deployed successfully (run make build-docs)

@p-offtermatt p-offtermatt requested a review from a team as a code owner November 30, 2023 12:16
@p-offtermatt p-offtermatt changed the title Add all md files in root dir to linkchecker docs: Add all md files in root dir to linkchecker Nov 30, 2023
@github-actions github-actions bot added the C:CI Assigned automatically by the PR labeler label Nov 30, 2023
@github-actions github-actions bot added the C:Testing Assigned automatically by the PR labeler label Nov 30, 2023
@@ -1,135 +0,0 @@
# Differential testing for Interchain Security 'core' protocol

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This README is obsolote very soon (https://github.com/cosmos/interchain-security/blob/df7ea65610458eaf964bbaf75f7a00b8003f89bf/tests/mbt/README.md), so I just deleted it instead of going through and fixing the links.

Copy link
Contributor

Choose a reason for hiding this comment

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

We should ignore the .changelog folder when we check .md links. We already check the results, i.e., CHANGELOG.md.

@@ -64,9 +64,9 @@ Date: June 1st, 2023

Unlike prior releases, the ICS `v2.0.0` release will be based on the main branch. `v2.0.0` will contain all the accumulated PRs from the various releases below, along with other PRs that were merged, but not released to production. After `v2.0.0`, we plan to revamp release practices, and how we modularize the repo for consumer/provider.

Upgrading a provider from `v1.1.0-multiden` to `v2.0.0` will require state migrations. See [migration.go](./x/ccv/provider/keeper/migration.go). See the provider module's `ConsensusVersion` in [module](./x/ccv/provider/module.go)
Upgrading a provider from `v1.1.0-multiden` to `v2.0.0` will require state migrations. See [migration.go](../x/ccv/provider/keeper/migration.go). See the provider module's `ConsensusVersion` in [module](../x/ccv/provider/module.go)
Copy link
Contributor

Choose a reason for hiding this comment

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

This will end up in CHANGELOG.md and then the links will be broken. You can test that by running unclog build > CHANGELOG.md.

# This is due to the markdown-link-check action
# not having an exclude parameter, see
# https://github.com/gaurav-nelson/github-action-markdown-link-check/issues/38
- name: Remove folders that we do not want to check
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this going to just remove an entire folder from the repo? See #1464 as a potential solution.

Copy link
Contributor Author

@p-offtermatt p-offtermatt Dec 1, 2023

Choose a reason for hiding this comment

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

It will remove it, but only in the context of this workflow - maybe I'm wrong, but your PR just changes the trigger for the workflow not to trigger on changes to .changelog, but the check still considers files in the .changelog folder when it triggers, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In this PR, note the folder is only removed for this particular workflow, so it doesn't negatively impact other workflows

@p-offtermatt
Copy link
Contributor Author

I adjusted this.
Because the markdown link checker doesn't have an option to exclude directories, what I do now is to just check two patterns:
all files under docs/docs (where ADRs live)
*.md (i.e. .md files in the root directory)

This needs two separate jobs (which is not too bad, it helps diagnose errors slightly, but takes an extra line in the checks)

Copy link
Contributor

@mpoke mpoke left a comment

Choose a reason for hiding this comment

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

LGTM

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

Copy link
Contributor

@MSalopek MSalopek left a comment

Choose a reason for hiding this comment

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

LGTM (administrative approval)

auto-merge was automatically disabled December 5, 2023 14:37

Pull request was closed

@p-offtermatt
Copy link
Contributor Author

Closed and will reopen due to technical reasons related to merge queue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:CI Assigned automatically by the PR labeler C:Testing Assigned automatically by the PR labeler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants