-
-
Notifications
You must be signed in to change notification settings - Fork 13
fix(defaults): add default path for readme and action for cli usage #267
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -42,6 +42,7 @@ export type ArgvOptionProperties = { | |||||
| describe: string; | ||||||
| parseValues?: boolean; | ||||||
| type?: string; | ||||||
| default?: string; | ||||||
| }; | ||||||
| }; | ||||||
| /** | ||||||
|
|
@@ -73,6 +74,7 @@ argvOptions[ConfigKeys.pathsAction] = { | |||||
| alias: ['pathsAction', 'action'], | ||||||
| type: 'string', | ||||||
| describe: 'Path to the action.yml', | ||||||
| default: './action.yml', | ||||||
|
||||||
| default: './action.yml', | |
| default: 'action.yml', |
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.
This workflow change appears to be unrelated to the PR's stated purpose of adding default paths for CLI usage. The change removes the branch restriction (
github.ref_name == 'main'), allowing NPM releases from any branch (main, next, beta, *.x). However, this contradicts the semantic-release configuration in package.json (lines 107-114), which only defines main, next, and alpha as release branches. This discrepancy could lead to unexpected release behavior or failed releases from branches not configured in semantic-release. Additionally, this change is not mentioned in the PR description and should either be removed or documented in a separate PR focused on release configuration changes.