© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Christopher,
From the git workflow perspective with launchpad you would need to:
1) clone a git repository locally
2) make your changes
3) create a merge proposal
➜ testrepo git init
Initialized empty Git repository in /tmp/testrepo/.git/
➜ testrepo git:(master) ✗ touch testfile && git add testfile && git commit -m 'testcommit'
[master (root-commit) 4b8cb6c] testcommit
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 testfile
➜ testrepo git:(master) git push --set-upstream git+ssh:
Counting objects: 3, done.
Writing objects: 100% (3/3), 221 bytes | 221.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To git+ssh:
* [new branch] master -> master
Branch master set up to track remote branch master from git+ssh:
This will create a repository under https:/
https:/
After that you can go to
https:/
And change the project "target" from "Personal" to "Project" and search for, e.g., "maas". In this example I will use "testrepo" as a target project instead.
As a result your repo URL will look like this: https:/
This is because of how launchpad URLs are structured - lp is project-oriented
https:/
https:/
You can then create a merge proposal either via web ui or by visiting a URL directly:
https:/
Normally, before creating merge proposals, you also create a feature branch so that your own repo is structured and you can track multiple merge proposals in different branches.
You can see how other people use the same approach:
https:/
I hope that helps.