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
We have discovered that private gems are hard to work with from a permissions perspective across Github repositories. The code in this repository is not super secret, so we're opening it up to the public. We will not publish a gem, because we don't see this code as something that is useful in a generic way that others can build dependencies upon.
This means we need to do a few things to make this possible:
I've added the status checks requirement before merging.
Note that each action is listed there separately, so when we add a new Ruby version, it needs to be added there too.
We have discovered that private gems are hard to work with from a permissions perspective across Github repositories. The code in this repository is not super secret, so we're opening it up to the public. We will not publish a gem, because we don't see this code as something that is useful in a generic way that others can build dependencies upon.
This means we need to do a few things to make this possible:
main
branch (instead ofstable
) #5main
branch by mandating CI passes before merge (@wvengen should have permission to set this up)Things can be checked off the list, or we can convert some to issues themselves if they become PRs or need more of their own context / decisions.
The text was updated successfully, but these errors were encountered: