Skip to content

Markdown linter#5494

Merged
mergify[bot] merged 57 commits intosigp:unstablefrom
chong-he:markdown-linter
May 24, 2024
Merged

Markdown linter#5494
mergify[bot] merged 57 commits intosigp:unstablefrom
chong-he:markdown-linter

Conversation

@chong-he
Copy link
Member

@chong-he chong-he commented Mar 27, 2024

Issue Addressed

Additional Info

@chong-he chong-he added the work-in-progress PR is a work-in-progress label Mar 27, 2024
Copy link
Member

@AgeManning AgeManning left a comment

Choose a reason for hiding this comment

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

Nice!

Could we add it into the code-check test?

I recall grouping things improved the speed of CI and it seems this could fit under that test?

@chong-he
Copy link
Member Author

Nice!

Could we add it into the code-check test?

I recall grouping things improved the speed of CI and it seems this could fit under that test?

I will look into it, thanks!

@jxs
Copy link
Member

jxs commented Mar 29, 2024

can we run this conditionally, i.e. only for changes in markdown files?

@chong-he
Copy link
Member Author

can we run this conditionally, i.e. only for changes in markdown files?

Yes, the VALIDATE_MARKDOWN: true is to only run this for markdown file. Got it from: https://github.com/super-linter/super-linter?tab=readme-ov-file#configure-super-linter which states:

If you set any of the VALIDATE_[LANGUAGE] variables to true, super-linter defaults to leaving any unset variable to false (only validate those languages).

Copy link
Collaborator

@dapplion dapplion left a comment

Choose a reason for hiding this comment

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

Purely formating changes, nothing controversial. They look good! I welcome the linter

@AgeManning
Copy link
Member

Probably need to pass the actual linter first

@chong-he
Copy link
Member Author

chong-he commented Apr 3, 2024

Probably need to pass the actual linter first

Yes I am still figuring out to make it pass the CI. I will also make the linter to be in the same check with code-check later

@dapplion dapplion self-requested a review April 3, 2024 02:53
@@ -30,17 +30,17 @@ is not the case for attestations from the _previous_ epoch.

```
Copy link
Member

Choose a reason for hiding this comment

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

try adding text here

@mergify
Copy link

mergify bot commented May 21, 2024

requeue

✅ This pull request will be re-embarked automatically

Details

The followup queue command will be automatically executed to re-embark the pull request

@mergify
Copy link

mergify bot commented May 21, 2024

queue

🛑 The pull request has been removed from the queue default

Details

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

mergify bot added a commit that referenced this pull request May 21, 2024
@jimmygchen jimmygchen added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels May 21, 2024
@michaelsproul
Copy link
Member

@Mergifyio requeue

@mergify
Copy link

mergify bot commented May 23, 2024

requeue

✅ This pull request will be re-embarked automatically

Details

The followup queue command will be automatically executed to re-embark the pull request

@mergify
Copy link

mergify bot commented May 23, 2024

queue

🛑 The pull request has been removed from the queue default

Details

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

mergify bot added a commit that referenced this pull request May 23, 2024
@michaelsproul
Copy link
Member

Ah, looks like this is failing to merge because of some formatting issues in unstable. @chong-he can you back-merge unstable to this branch, and then get CI passing again? 🙏

https://github.com/sigp/lighthouse/actions/runs/9200347323/job/25306765265

@michaelsproul michaelsproul added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-merge This PR is ready to merge. labels May 23, 2024
chong-he and others added 2 commits May 23, 2024 10:26
Merge unstable to markdown branch
@chong-he
Copy link
Member Author

Ah, looks like this is failing to merge because of some formatting issues in unstable. @chong-he can you back-merge unstable to this branch, and then get CI passing again? 🙏

https://github.com/sigp/lighthouse/actions/runs/9200347323/job/25306765265

Done, thanks!

@chong-he chong-he added ready-for-merge This PR is ready to merge. and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels May 23, 2024
@jimmygchen
Copy link
Member

@mergify queue

@mergify
Copy link

mergify bot commented May 23, 2024

queue

🛑 The pull request has been removed from the queue default

Details

The pull request conflicts with at least one pull request ahead in queue.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

@michaelsproul
Copy link
Member

@Mergifyio requeue

@mergify
Copy link

mergify bot commented May 24, 2024

requeue

❌ This pull request head commit has not been previously disembarked from queue.

@michaelsproul
Copy link
Member

@Mergifyio queue

@mergify
Copy link

mergify bot commented May 24, 2024

queue

✅ The pull request has been merged automatically

Details

The pull request has been merged automatically at 3070cb7

@mergify mergify bot merged commit 3070cb7 into sigp:unstable May 24, 2024
@chong-he chong-he mentioned this pull request May 25, 2024
@chong-he chong-he deleted the markdown-linter branch June 16, 2024 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infra-ci ready-for-merge This PR is ready to merge. v5.2.0 Q2 2024

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants