+1 I'm in favor of being liberal with experimental things. Just name it something someone won't mistake for anything stable or release-ish, "dev-githubactions" or whatever. And delete it if/when you're no longer using it.
On Fri, Aug 2, 2019 at 9:22 AM Gray, Jonathan <[email protected]> wrote: > Nope, I've done similar things in the past for Jenkins (and it's on my > todo list again, so I'm curious what you find out). > > Jonathan G > > > On 8/2/19, 8:54 AM, "ocket 8888" <[email protected]> wrote: > > I wanted to mess around with GitHub actions for Traffic Control - but > they're in beta and I haven't been granted access to them as a GitHub > user. > But Apache as an organization has. So basically, I can mess with them > on > the ATC repo, but not on my personal fork. > > For that purpose, I was wondering if anyone would have a problem with > me > making a branch where I could tinker with it a bit? I can't imagine > how it > would affect anything outside of the branch, and at any rate the > branch can > be deleted at any point. > > > (GitHub Actions: https://github.com/features/actions) > > >
