Arxiu de la categoria: tips
Once in a while you encounter branches that are have been over-used, i.e. multiple persons added commits there for unrelated issues.
How to get around/solve that? I’m glad you ask :-)
Today I was facing something similar at work, where the messed up branch in question had some commits already merged into master but there were some important other parts to be extracted from it.
So I used three tools:
git log --graph --decorate --pretty=oneline --abbrev-commit --all(with an alias
- a git graphical visualizer (gitg for instance)
- a simple plain text editor (gedit for instance)
git fulllog in a terminal and copy & paste as much information as you need into the text editor.
Fire up the git graphical visualizer and check each relevant commit what’s doing.
Once you know what it is about annotate each commit so you know which commits relate together, i.e. from
ae0ee04 My commit message
ae0ee04 11111 My commit message
This way once everything is annotated is really simple to just grab all the
11111 commits and
git cherry-pick them in a new branch :-)
Pro tip: as you are editing a plain text file you can keep removing lines and adjusting the indentation, suddenly you realize how things keep fitting together!
Maybe everyone is already aware of them, but just in case…
zc.buildout is THE building block that assembles Plone together.
It’s been around for quite a while (+10 years) and it has plenty of features.
Two of them which I’m enjoying a lot lately are:
./bin/buildout install code-analysis
install allows you to override which parts are going to be installed and thus it allows, like in the example above, reduce the amount of packages to fetch and things to build. Which for something like jenkins.plone.org can make quite a lot of sense to use it more and more.
annotate outputs the complete configuration that buildout will use as if it was everything in a single file. This is great for debugging “why my configuration is overriden or not being used at all” kind of errors.