Convert master/feature branch error into warning

[hnyman]

Having the PR issued from a feature branch makes things much easier, e.g. with editing the pr. So it is a strong recommendation.

But the source branch makes no actual difference to the code quality or the commit contents. Handling Ng that as error seems too harsh to me.

Please convert the "from master" error into a warning.

Example
https://github.com/openwrt/packages/actions/runs/21026058778/job/61403662110

[GeorgeSapkin]

Thanks for the feedback. The difference is that when contributors don't respond to feedback, it's not possible to rebase or fix a PR since master branches are protected.

There's already an option to disable the check:

• https://github.com/GeorgeSapkin/hyperstickler#check_branch

I just need to tag a new version that includes the change 🐌

[hnyman]

Thanks. Waiting for the change.

The difference is that when contributors don't respond to feedback, it's not possible to rebase or fix a PR since master branches are protected.

I know. The rebase is handy recent functionality in Github, but not that essential that a hard stop due to prevented capability. Many/most PRs get merged without need to for manual rebasing. Warning about master branch would still be good, but error is too harsh.

I have been handling PRs here since 2014, long before the GUI rebase PR functionality even was in Github... I have over 2700 commits in openwrt/packages, many of them PR merges, so I have seen pretty much all possible mishaps related to handling PRs in OpenWrt context ;-)

(And as total a bit over 4600 commits in all OpenWrt repos together.)

[GeorgeSapkin]

I tagged a new release with the check_branch input:

• https://github.com/GeorgeSapkin/hyperstickler/releases/tag/v1-rc.1