How to make nRF Connect SDK submit to other code management servers (such as bitbucket,Not github), And continue to use Git to manage this code?

[gavin.rf]

How to make nRF Connect SDK submit to other code management servers (such as bitbucket,Not github),
And continue to use Git to manage this code?

I will modify the content of the NRF Connect SDK and push the modification to the Bitbucket repositories.
I don't want to use GibHub, Because the Bitbucket used by my company.
I have read the Development model: developer.nordicsemi.com/.../dm_adding_Code.html
But unfortunately, what is introduced here is based on GitHub's own fork, and I need to push the code to the company's BitBucket server.
I did not find a way to manage SDK and my own applications based on BitBucket/Git.

[Raoul]

Hi,

If you are planning to make modifications to nRF Connect SDK itself (or, one of the repos that make up NCS to be precise), you'll be forking the repo - workflow 3.

This process is more closely described here: Forking a repository of the nRF Connect SDK. Please note the difference between the GitHub fork feature and forking as a concept. Since you will be using Bitbucket, you will have to fork "manually" by creating a new repo, cloning, and configuring remote, as described on Stack Overflow.

(After that, if/when you want to update your NCS version you'll also have to manually pull changes from the GitHub remote, and push them to your Bitbucket remote.)

So, continuing to use git is not an issue - the git repository itself is separate from GitHub and Bitbucket (solutions for hosting a remote repository).

If you are making a complicated set of changes to multiple repos in the nRF Connect SDK, you could consider modifying remotes in your West Manifest to fit your needs, so that you can use West update (which coordinates the different repo versions) for convenience. If you leave your West manifest unmodified, west update will always pull from GitHub.

Finally, as Henry says, if you are only planning to update your own sample/application (prj.conf, cmakelists.txt source files, etc.) then you can just put those files in a Git repo on Bitbucket (remember to add build* to your .gitignore), and forget about the rest.

Hope this answers your question!

Best regards,

Raoul Pathak

[gavin.rf]

Thank you for your help. I will try to manage the sdk on the company's bitbucket with your guidance. Thank you again. At present, I am busy with business programming and debugging, and I will try later. It is unavoidable to modify the sdk. If I can't manage the changes on the sdk well, it is really annoying

[Raoul]

I understand. I hope you can manage!

Best regards,

Raoul