Repository navigation
feat(rogue): add a spelling mistake - #6
Open
StaticRocket wants to merge 7 commits into
Open
StaticRocket wants to merge 7 commits into
StaticRocket wants to merge 7 commits into
Conversation
StaticRocket
force-pushed
the
test/lint
branch
3 times, most recently
from
May 16, 2025 20:27
c96d8f2 to
3415af1
Compare
StaticRocket
force-pushed
the
test/lint
branch
2 times, most recently
from
May 16, 2025 21:13
7e2a31f to
ca034bc
Compare
StaticRocket
force-pushed
the
master
branch
2 times, most recently
from
May 16, 2025 21:37
1cc4ca5 to
29d043d
Compare
|
New issues found with check_toc_txt.py: |
StaticRocket
force-pushed
the
master
branch
3 times, most recently
from
June 13, 2025 20:17
5ac75d5 to
12d1925
Compare
|
New issues found with check-files.sh: |
|
New unreachable files found with check_files.py: |
StaticRocket
force-pushed
the
master
branch
2 times, most recently
from
May 7, 2026 22:48
4a44820 to
0edc98d
Compare
StaticRocket
force-pushed
the
test/lint
branch
7 times, most recently
from
May 7, 2026 23:48
7068b80 to
c80639b
Compare
|
New unreachable files found with check_files.py: |
StaticRocket
force-pushed
the
master
branch
4 times, most recently
from
June 18, 2026 21:18
b89c801 to
20d025a
Compare
StaticRocket
force-pushed
the
master
branch
5 times, most recently
from
July 8, 2026 23:58
8471111 to
a7f332f
Compare
We can avoid running this entirely if none of the files we're looking for have been modified. I wish we could use a yaml anchor or something to prevent duplicating the patterns here, but it doesn't seem like that's an option as the other workflow only wants strings. Signed-off-by: Randolph Sapp <rs@ti.com>
As much as I liked the simplicity in the old workflow definition, it had issues when pushing container updates in combination with source updates. The docker and build workflows would race. Needs explicit checks for "!failure() && !cancelled()" because once one thing in a needs chain is unsatisfied (or skipped) GitHub would prefere to invalidate the entire chain. Signed-off-by: Randolph Sapp <rs@ti.com>
Well, version pinning requires inline comments that frequently make lines go over the recommended 80 character length. Disable this check for all the workflow files preemptively. Signed-off-by: Randolph Sapp <rs@ti.com>
It's generally advised to pin workflow versions to avoid issues with floating tags or manipulated releases. Dependabot can still track and upgrade things if we add inline comments. Signed-off-by: Randolph Sapp <rs@ti.com>
Work around an upstream issue [1] with a manual pin for now. Hopefully this won't break future dependabot checks. [1] vale-cli/vale-action#158 Signed-off-by: Randolph Sapp <rs@ti.com>
Apparently you can ignore a cancel request with the always() function. This is only documented on a single page in the GitHub workflow docs that I found in passing checking other garbage. I assume this means you could also bypass concurrency flags with this in place. Don't really want to find out. Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Randolph Sapp <rs@ti.com>
|
New unreachable files found with check_files.py: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Check the ci pipeline for vale.