Feature: repository ruleset event type not defined

[rbtcollins]

From cbrgm/githubevents#94 (comment) - GitHub are now creating repository rulesets by default rather than branch protection rules (via the UI at least).

API definition.

[gmlewis]

Would you like to create a PR for this, @rbtcollins , or shall I open this up to other contributors to this repo?

[rbtcollins]

I don't think I have an active google CLA with my current employer, and last time I discussed such with legal we got stuck. So I'm not sure I can commit to a PR.

[gmlewis]

This would be a great PR for any new contributor to this repo or a new Go developer.
All contributions are greatly appreciated!

Feel free to volunteer for any issue and the issue can be assigned to you so that others don't attempt to duplicate the work.

Please check out our CONTRIBUTING.md guide to get started. (In particular, please remember to go generate ./... and don't use force-push to your PRs.)

Thank you!

[unamdev0]

Hi @gmlewis @rbtcollins I'd like to work on this

[gmlewis]

Hi @gmlewis @rbtcollins I'd like to work on this

Thank you, @unamdev0 !
It's yours.

[unamdev0]

Hi @gmlewis, one small doubt, if you check the properties of repository_ruleset object here, there's a condition key which is given as object or null, but what'll be the keys for this object are not given.

What should be done in this case? should I declare it as map[string]interface{} field as to accommodate anything that comes inside condition object

[gmlewis]

What should be done in this case?

When we don't know what the object will be, we typically use a json.RawMessage to represent it so that it can be more easily unmarshaled after its type is known (by the user after processing the rest of the struct).

Here are some existing examples you can take a look at from this repo:

[unamdev0]

Cool, will use this