We are considering upgrading our Github account from a free to teams version so as to use branch protection rules on the master branch, specifically requiring a pull request to merge into the master. Just wondering if this will have any unintended consequences when doing github interactions from within Oxide. I’m hoping the same code commit/merge restrictions will persist from within Oxide as defined in Github?
1 Like
Hi @martin
Our version control integrations do support Branch protection - so that should just work right out of the box.
I cannot imagine that anything will change on our side when you upgrade from Free to Teams, but I will confirm with the relevant team on our side and get back to you
[UPDATE] - Confirmed that there should be no issues with upgrading, and also confirmed that our internal apps run on a Github Teams Organization based integration, and that works perfectly.