Versions Compared

Old Version 3

changes.mady.by.user Tijmen Daatselaar

Saved on

compared with

New Version Current

changes.mady.by.user Tijmen Daatselaar

Saved on

Key

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

...

You can navigate to elements that are created or updated using CTRL + click. You can select all or a subset of changes in a certain branch to be committed. Migration changes are of an informative kind: they are selected by default , and cannot be unselected or reverted. 

ActionDescription
RefreshUse the refresh button in the title bar on the top right to refresh the list of pending changes.
FilterCan be used to filter in the tree of changes. You can use the filter on the action (create, update, delete) element type, element name, and author. 
Revert

Before committing all changes, you should check them first whether to see if they are still relevant. It might be possible that some of the changes are incorrect or obsolete, and you don't want to process them. You can do this by reverting the changes. This will bring the element in back to the state of the previous revision. Note that reverting is different from unselecting the change - ; the latter action will only postpone the registration, but it will still be still part of your branch. Be careful, ; reverting changes cannot be undone.

Commit message

In the commit section there is a commit message, this message is required. This message is important because it provides insight in the reason changes were made and what changes were made to your project(s). The message will appear in the commit history view.  The registration message cannot be altered once the changes are committed.

Tip

It's considered as a good practice to keep the message short and start the commit message with a verb. I.e., "Create repository,",   "Add feature x," , and "Fix component y." . You may also use emoji's emojis in the commit message, such as 🚑 for a critical hotfix. 

TagsNext to the registration message are the tags. Tags are used to put a label on a specific revision. For instance a , the tag 'RC_1' could indicate that this revision is release candidate 1. You can put multiple tags on a revision. Tagging can be done during change registration, but you can change, add, or remove tags at any time from the commit history view.