git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Rebase

From
AGAl Grant <bigal.nz@gmail.com>
Date
Jan 19, 2025, 05:29 UTC
Message-ID
<CAODtcdcTjquNUBaTWKzyy54J5NoH7WO+9uMzJ+wWRDf0Na3OPA@mail.gmail.com>
Hello,
I am looking for some assistance rebasing please.

I have a feature branch which has the many recent commits and a main branch which has not had a commit for a long time. I want to make the code in the feature branch the code in the main branch.

I think a rebase is the command I need, but the exact steps I am not sure of.
I did try this:
1. Sync both branches with remote (github)
2. git checkout feature
3. git rebase main
That resulted in the following perge conflicts:

PS C:\Users\AlGrant\andrej_branch\test_fft> git rebase main error: could not apply 1f893dc... Make project runnable on Linux Resolve all conflicts manually, mark them as resolved with "git add/rm <conflicted_files>", then run "git rebase --continue". You can instead skip this commit: run "git rebase --skip". To abort and get back to the state before "git rebase", run "git rebase --abort". Could not apply 1f893dc... Make project runnable on Linux Auto-merging src/kiwitracker/sample_processor.py CONFLICT (content): Merge conflict in src/kiwitracker/sample_processor.py Auto-merging src/kiwitracker/common.py CONFLICT (content): Merge conflict in src/kiwitracker/common.py PS C:\Users\AlGrant\andrej_branch\test_fft> git rebase --abort

Which I have now aborted. I dont understand why I even have to deal with merge conflicts when I want to keep the code in feature and make it main.

Help.
Thanks
Al
Next: brian m. carlson
Message 1 of 6 in “Rebase”
  1. Al GrantJan 19, 2025
  2. brian m. carlsonJan 19, 2025
  3. Al GrantJan 19, 2025
  4. D. Ben KnobleJan 19, 2025
  5. brian m. carlsonJan 20, 2025
  6. Al GrantJan 20, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.