Repository rules - Import/Export + History Public Beta!

[patrick-knight]

Is this you?
Is it hard to know who changed your perfect ruleset, and you need to get it back to the way life was?

Are you longing for an easy way to move your rules to a different org?
Or share them with your friends on the internet?

Now in public beta

Import & Export

It's easier to share and reuse rulesets, with the ability to import and export them as a JSON file. So you can build an internal library of rulesets or publicly share you favorite ruleset configs. Which is what we're doing!

Based on some best practices so you can quickly get started with rules in our ruleset recipe repo!

History

Did another admin remove a status check? Was the number of reviews changed? When did that happen? How do I fix this mess?

We're adding a history experience for GitHub Enterprise Cloud customers so you can track changes and revert to historical versions of a ruleset. Before this you would need to parse the audit log to find modifications to a ruleset but might not have permissions to the log or even want to dig through it.

Now, it's easy to see who changed a ruleset, when it happened, and what changed. Then, quickly get back to a known good state.

[llucax]

I don't see the options import or export ruleset. Is there anything I need to do to enable them?

[patrick-knight]

Hey @llucax looks like we missed a few folks in the initial rollout, can you try again? If it's still not working can you let me know so we can do some more investigation.

[llucax]

Yeah, I can see it now, awesome, thanks!

[jurgis-sipols]

clicking feedback might open in a new tab, imported ruleset was not saved :)

[jurgis-sipols]

although, state was saved when I clicked back, so that's good 👍🏻

[samus-aran]

Hi @AnnaPnunes , thanks for participating!

We’re happy you’re here but let’s not divert this discussion as this conversation is off-topic. Please open up a separate discussion so that we can look at your query there. 👍

We take our Code of Conduct very seriously and want to help ensure that everyone has a good experience free of antagonism and harassment. Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting. 👍

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[oussama-akhatar]

Good luck

[CoenraadS]

I would love to be able to import multiple rulesets at once. I don't need to review them before creation.

[patrick-knight]

Using the ruleset APIs is probably going to be you best bet to due multiple creations without the same validations the UI provides.

[PaarthShah]

I want to be able to see the history of rules that were deleted as well; plenty of chaos can be caused by that.
Perhaps also notifications to repo admins/org admins when a ruleset is created/deleted, with a backup of the ruleset json for re-import?

[patrick-knight]

There are a few ways you could handle that today with the audit log or webhooks to have historical information about the deleted ruleset.

Audit log:

Webhook:

[dchien234]

When importing rulesets, it might have missed the Bypass list (for e.g. org admin). Not sure if this is intentional or a bug.

[book000]

I don't know why, but this problem seems to occur only when importing into a ruleset in a repository created under “user”.
When importing into rulesets in repositories under “organization”, the bypass list is set properly.

[norwd]

I'm a huge fan of this feature, but the rest API endpoint only allows specifying each field as a body parameter, not as a JSON body. Is there any chance that the rest API will accept the same JSON schema so that I can start automating this even further. Currently I have a bunch of rule sets saved as gists and I'd like to be able to roll those out in one go, otherwise I have to upload the same file to each repo manually :(