You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
amannn/action-semantic-pull-request is an ideal workflow to check PR Validation, it is followed by semantic style, as for thehanimo/pr-title-checker, we need to write the pattern in json config, and actually thery are not followed by semantic style tyle, and we have to maintain another json config, which is no-needed.
Also this project is more active than hehanimo/pr-title-checker, which means this project is more stable to be maintained. We should choose a stable and active action as our github workflow, otherwise if any bugs happened, we will get into troubles and hard for us to fix, which leads us to change our actions repeatedly, this is not what maintainers want to see.
The text was updated successfully, but these errors were encountered:
Xunzhuo
changed the title
ci: remove PR Title Checker and update it with semantic-pull-request
ci: replace PR Title Checker with a stable action
May 3, 2022
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions.
replace pr title validator
compared with thehanimo/pr-title-checker:
amannn/action-semantic-pull-request is an ideal workflow to check PR Validation, it is followed by semantic style, as for thehanimo/pr-title-checker, we need to write the pattern in json config, and actually thery are not followed by semantic style tyle, and we have to maintain another json config, which is no-needed.
Also this project is more active than hehanimo/pr-title-checker, which means this project is more stable to be maintained. We should choose a stable and active action as our github workflow, otherwise if any bugs happened, we will get into troubles and hard for us to fix, which leads us to change our actions repeatedly, this is not what maintainers want to see.
The text was updated successfully, but these errors were encountered: