warmachine028

{"version":1,"resource":"file:///d:/Programs/university-skills/OS/12_maximum_3.sh","entries":[{"id":"wrzK.sh","timestamp":1649270512061},{"id":"o9S8.sh","source":"undoRedo.source","timestamp":1649270512935},{"id":"4Lmn.sh","timestamp":1649270516156},{"id":"HVF5.sh","timestamp":1649270529310},{"id":"gZd2.sh","timestamp":1649270530364},{"id":"JdBA.sh","timestamp":1649270534730},{"id":"Dx4H.sh","timestamp":1649270535536},{"id":"LFxx.sh","timestamp":1649270537719},{"id":"gTTX.sh","timestamp":1649270538580},{"id":"BrCv.sh","timestamp":1649270559511},{"id":"VFQi.sh","source":"undoRedo.source","timestamp":1649270561195},{"id":"kpx9.sh","timestamp":1649270562628},{"id":"wMO0.sh","timestamp":1649270565017},{"id":"Z7vE.sh","timestamp":1649270566189},{"id":"xGPj.sh","timestamp":1649270576641},{"id":"GLVB.sh","timestamp":1649270581639},{"id":"bapV.sh","timestamp":1649270582606},{"id":"woZc.sh","timestamp":1649270584057},{"id":"AnRt.sh","timestamp":1649270585204},{"id":"MWQc.sh","timestamp":1649270587333},{"id":"KH85.sh",

scmx

Example list of first words to use in a git commit title

I like writing well-formed git commits that explain the intention behind why a code change was made.

Check out Chris Beams excellent How to Write a Git Commit Message if you haven't read it.

Anyway, for a project I've been working on I've gathered up 900+ commits that hold up a pretty high quality (except for one 😁). Let's look at some trends about these commits!

Most common first words in commit titles of a project

CMCDragonkai

Exporting Modules and Functions from Python __init__.py

Any directory with __init__.py is considered a package in Python.

Any python files inside a package is considered a module.

Modules contain functions and other bindings that is always exported.

If you are outside the package, and you want to import a module from a package:

msrose

Combining two git repositories

Use case: You have repository A with remote location rA, and repository B (which may or may not have remote location rB). You want to do one of two things:

• preserve all commits of both repositories, but replace everything from A with the contents of B, and use rA as your remote location
• actually combine the two repositories, as if they are two branches that you want to merge, using rA as the remote location

NB: Check out git subtree/git submodule and this Stack Overflow question before going through the steps below. This gist is just a record of how I solved this problem on my own one day.

Before starting, make sure your local and remote repositories are up-to-date with all changes you need. The following steps use the general idea of changing the remote origin and renaming the local master branch of one of the repos in order to combine the two master branches.