fregante/Title Replacer
Replaces and formats keywords in titles of issues and PRs.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| pattern | What to search in titles. Comma-separated or line-separated, surrounding spaces are ignored. If it starts with a /, it is treated as a regular expression. (example: fix, bug, feat) | — | — |
| pattern-path | The path to read the patterns from. It can be a file (comma-separated or line-separated) or a directory, where all the file *names* will be used (without the extension) | — | — |
| replacement | What to replace the pattern with. Use $0 for the matched pattern, or $1, $2, etc. if you're using a regular expression with groups. (example: '`$0`') Note that if you use this action to wrap keywords like '`$0`', you should also use `trim-wrappers: true` or else keywords will be wrapped twice. | — | "" |
| trim-wrappers | The surrounding characters to trim when replacing the pattern, for example the replacement can drop the quotes in `"hippo"` when the pattern is just hippo. Example: '[]{}"' Example: 'true' means ()[]{}"'`<> | — | "" |
| uppercase-first-letter | Whether to uppercase the first letter of the title | — | true |
| dry-run | If true, show what changes would be made without actually making them | — | false |
| allow-override | If true, reduces frequency at which it tries to apply the replacements, in order to allow the user to set a specific title even if it matches the pattern. This avoids frustrating user/action loops. NOT WORKING YET | — | false |
| token | The automatically-generated token, set this to \$\{\{ secrets.GITHUB_TOKEN \}\} | — | — |
Outputs
| name | description |
|---|---|
| changed | Whether the title was changed |
| title | The title after the replacements or the original title if unchanged |