-
Notifications
You must be signed in to change notification settings - Fork 23
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
Adding app-name-matcher to Action params #57
Conversation
@@ -0,0 +1,16 @@ | |||
name: "build" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pulled into separate CI step so it can pass and be required by GitHub Branch Protection Rules
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, love all the api improvements.
|
||
const changedFiles = await getChangedFiles(); | ||
core.info(`Changed files: ${changedFiles.join(', ')}`); | ||
const appsAffected = repoApps.filter(partOfApp.bind(null, changedFiles)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
potential behavior change here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to flag, but no change. Not sure why I did this though, it's unnecessarily clever 😅
What changed?
app-name-matcher
allows for directly matching app names or providing a regexmain.ts
so that nothing runs upon module import (important for testing)Test plan
build
CI step passes