reaction-link/Lint Pull Request

Lint the pull request structure and leave a comment suggesting changes if linting fails

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
access-token	Token with triage permissions or GITHUB_TOKEN	yes	—
token-login	Username of the GitHub user	yes	—
github-event	toJSON of github.event (event triggering the action)	yes	—
use-greetings	JSON string array to use for randomly selected greetings (used in comment body, runs through JSON.parse)	—	["Hello @{name},\n"]
use-approval-labels	JSON string array to use for labeling linted pull request (runs through JSON.parse)	—	["Good"]
use-title-regex	Regex string to use for linting the pull request title	—	\w+
use-description-regex	Regex string to use for linting the pull request description	—	\w+
use-title-regex-flag	Regex flag to use for linting the pull request title (Use empty string for none)	—	g
use-description-regex-flag	Regex flag to use for linting the pull request description (Use empty string for none)	—	g
use-problem-title	Template string to use for highlighting a title that failed to pass (used in comment body). Template-Literals: {title}	—	- The title `{title}` is not the format I expected.
use-problem-description	Template string to use for highlighting a description that failed to pass (used in comment body). Template-Literals: {body}	—	- The description `{body}` is not the format I expected.
use-explanation-title	JSON string array to describe rules to pass linting for the pull request title (used in comment body, runs through JSON.parse)	—	["- There must be a title","- Use proper capitalization"]
use-explanation-description	JSON string array to describe rules to pass linting for the pull request description (used in comment body, runs through JSON.parse)	—	["- There must be a description"]

Outputs

no outputs