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
In it's current state, the .sauced.yaml config file natively supports Github usernames and teams.
For the use case of my team, we use Bitbucket as our SCM and would appreciate native support for Bitbucket specific features as we don't have a notion of "Github Teams", as an example.
In general, it would be amazing if the config file (among other parts of the Pizza CLI) could support specificities in other SCM platforms, exposing it's capabilities to a larger audience.
Thanks! 😁🚀
The text was updated successfully, but these errors were encountered:
Hi @udaypatel1 - thanks for opening the issue! We currently don't have any plans to open up support in the Pizza CLI to other git providers like bitbucket or gitlab.
But we're very interested to hear how this would integrate with bitbucket. Can you give me some examples of how you imagine this working?
In this case, bitbucket requires that a specific team.yaml file be created so that the .bitbucket/CODEOWNERS file can reference a Team (similar to that of the native Github Teams defined in .sauced.yaml)
How would this be integrated with the current pizza workflow? There would ideally be an additional config parameter in .sauced.yaml which would identify the git provider, and adjust CLI actions accordingly. Or, of course, another design to implement this which may be better suited.
I'm not sure of the other bitbucket specific nuances for how they manage CODEOWNERS but if there is interest, I'd be happy to provide continued help!
Suggested solution
In it's current state, the
.sauced.yaml
config file natively supports Github usernames and teams.For the use case of my team, we use Bitbucket as our SCM and would appreciate native support for Bitbucket specific features as we don't have a notion of "Github Teams", as an example.
In general, it would be amazing if the config file (among other parts of the Pizza CLI) could support specificities in other SCM platforms, exposing it's capabilities to a larger audience.
Thanks! 😁🚀
The text was updated successfully, but these errors were encountered: