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

💡 Feature Request - Change SuperLinter to only run on changed docs #262

Closed
jtracey93 opened this issue Jun 16, 2022 · 0 comments · Fixed by #264
Closed

💡 Feature Request - Change SuperLinter to only run on changed docs #262

jtracey93 opened this issue Jun 16, 2022 · 0 comments · Fixed by #264
Assignees
@jtracey93

Comments

@jtracey93
Copy link
Contributor

jtracey93 commented Jun 16, 2022 •
edited
Loading

Describe the solution you'd like

Change SuperLinter to only run on changed docs

Describe alternatives you've considered

None

Additional context

As discussed on a recent internal sync call, we all agree this is too slow scanning everything now so would prefer it only scans the changed docs
@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Jun 16, 2022
@jtracey93 jtracey93 self-assigned this Jun 16, 2022
@jtracey93 jtracey93 changed the title 💡 Feature Request - Change SuperLinter to only run on changed docs 💡 Feature Request - Change SuperLinter & Link Checks to only run on changed docs Jun 17, 2022
@jtracey93 jtracey93 removed the Needs: Triage 🔍 Needs triaging by the team label Jun 17, 2022
@jtracey93 jtracey93 mentioned this issue Jun 17, 2022
Merged
9 tasks
@jtracey93 jtracey93 changed the title 💡 Feature Request - Change SuperLinter & Link Checks to only run on changed docs 💡 Feature Request - Change SuperLinter to only run on changed docs Jun 17, 2022
jtracey93 added a commit that referenced this issue Jun 17, 2022
@jtracey93
Fix #262, #259, #248 (#264)
468e2fd
@ghost ghost added the Status: Fixed label Jun 17, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jtracey93 jtracey93

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #262, #259, #248
1 participant
@jtracey93