Re: wget2 | Adding wiki as submodule to git repo (!494)

[@rockdaboot]

Tim Rühsen commented:


Hi @getjff :wave: 

Since you have developer status, you can push your code into the main 
repository - that makes collaboration a bit easier. E.g. co-devs can test / 
push / change commits easier. I can also not look into your pipeline output to 
see why it fails.

You can still work and experiment in your own repo. And when you are done and 
have a branch ready to be pushed, push it to the gnuwget/wget2 repository and 
open the MR.

** The git workflow for this**
I assume that your Gitlab wget2 repository is named "origin" (check with `git 
remote`).

Create a second remote linking to gnuwget/wget2 (named 'gnuwget') with
`git remote add gnuwget git@gitlab.com:gnuwget/wget2.git`.

Fetch from from gnuwget with `git fetch gnuwget` (I often do a `git fetch 
--all`).

Pushing a branch to gnuwget then looks like `git push gnuwget` or if you only 
want to work via gnuwget repo with a branch do `git push --set-upstream gnuwget 
name-of-your-branch`.

If something goes wrong, ask me on Matrix.

So I would like to ask you for:
- clean up the MR (remove all the obsolete commits or obsolete code)
- use the GNU style commit message format (see `git log` for examples)
- push your branch to gnuwget using a namespace scheme like 
"getjff-what-ever-you-want" or "jeffrey-..." (we used to use tmp-... but it 
seems better to have an own namespace for every developer)
- create a new MR for it and drop the old MR

Cheers, Tim

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnuwget/wget2/-/merge_requests/494#note_645614031
You're receiving this email because of your account on gitlab.com.