• Home
    • View
    • Login
    This page
    • Normal
    • Export PDF
    • Export Word
    • Attachments
    • Page Information

    Loading...
  1. Dashboard
  2. Build
  3. Build Group
  4. Archived
  5. Submit Repo

Page History

Versions Compared

Old Version 27

changes.mady.by.user Brian Beck

Saved on Oct 25, 2016

compared with

New Version 28

changes.mady.by.user Brian Beck

Saved on Oct 25, 2016

  • Previous Change: Difference between versions 26 and 27
  • Next Change: Difference between versions 28 and 29
  • View Page History

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The commit message for the changeset at the head of your branch is used as the commit message for the changeset that is integrated to the default branch of the upstream forest.

How do I update my branch with the latest upstream changes?

How should I push a branch?

The first time you push a new branch to the submission forest, you need to use the "--new-branch" option like this:

...

Once the problem is found, you may make further commits to your branch and push again to the submission forest.  Remember that the commit message from the head of your branch will be the one that is eventually used when your change is merged upstream.

...

How are changes from upstream brought into the submission forest?

...

Overview
Content Tools
ThemeBuilder

Terms of Use
• License: GPLv2
• Privacy • Trademarks • Contact Us

Powered by a free Atlassian Confluence Open Source Project License granted to https://www.atlassian.com/software/views/opensource-community-additional-license-offer. Evaluate Confluence today.

  • Kolekti ThemeBuilder Powered by Atlassian Confluence 8.5.23
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 289, "requestCorrelationId": "550a526be8c52fdc"}