AEMaaCS: can you do all git work in bitbucket/github and only push to adobe once the release branches are ready?

[jayv25585659]

as an example:

I just started work in this organization where all git work is done inside the Adobe repos. The vendor has said to me that "pull requests" (including peer review) can be done using the Adobe repo.

From what I've read, pull requests (including the ability to easily see the changes) are specific to github/bitbucket. Perhaps there's something I'm missing.

The vendor said peer review and pull request approval can be done in a terminal and I'm unsure on how to do that? (apparently working with adobe repos only is the AEMaaCS way)

--------------

I've only work on on-premise previously and 1 of them is AMS. From what I can see in the pipelines, they should be no reason we cannot use bitbucket as a working repo (new branches, pull requests, reverts and etc) and only push to Adobe repos when ready to deploy.

Thoughts?

Thanks!

[AMANATH_ULLAH]

@jayv25585659 

Yes, In AEMaaCS you can use Bitbucket/GIT for entire development including creating branches, Pull requests review etc and finally push the release branch or any other branch to Adobe repo when they are ready for deployment

[h_kataria · Accepted solution]

It is essentially about setting up the dev workflow which varies from project to project. If the client wants to use their git, adobe provides ways to do that. See this for e.g https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi... 
We use gitlab for all our development, testing, PRs etc. but we have automation in place to sync that to adobe repo.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/managing-code/gi... this gives a raw idea on how you would do it if you use your own git. 

[aanchal-sikka]

@jayv25585659 

I agree with you, without a UI its difficult to work with PR and reviews.

I would suggest you to use a separate github/bitbucket for development purposes. And when ready for deployment push the develop/main branches to Adobe git.

The history can be maintained in sync... https://jigarius.com/blog/multiple-git-remote-repositories