Greetings! I would like to request an option to exclude a list of repositories. The use case is sometimes we would like set up other repositories with different settings (using an individual developer or an organization). I might work on a PR on my free time regarding this matter.

Due to the max limit of records per page of 100 (#5), we need to implement iteration with pagination to support 100+ repositories (public and private).

Greetings! Sometimes, it is unnecessary to show log outputs since they can have sensitive information that needs to be private. Others might already use this workflow in a public repository and that means they could leak sensitive information about their private repos.

The settings I would like to be able to control are:

Repo level

• Require contributors to sign off on web-based commits
• Always suggest updating pull request branches

Branch protection level

• Dismiss stale pull request approvals when new commits are pushed
• Require approval from someone other than the last pusher
• Require conversation resolution before merging
• Require signed commits
• Require linear history

But in general it would be best if this contained all possible settings

I suggest that we have more control over the settings for branch protection, I suggest having options like BRANCH_PROTECTION: true (default: false - if false will remove the branch protection) and for other options, if the setting will have null as a value it should somehow unselect the specific settings regarding branch protection. @kbrashears5 what do you think? please let us know. Thank you.

Greetings @kbrashears5, I find this workflow very useful in our use cases. May I know if can we include private repositories too? Let us know. Thank you.

This is a really great action! Thanks for making it. Any plans to add support for multiple branch protection rules? Our use case would be to add one for the main branch, and another for our staging branch with differing rules between them.