Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: projects / code-skeleton / features /

gitignore.mdwn

It seems many projects in GNOME use git.mk to generate the .gitignore file. But many others don’t, and it’s okay: You can just make your own file.

In any case, putting the Gedit backup file pattern there is wrong.

For now, my skeletons will include only build files in that file. man gitignore explains where each pattern belongs. I can add instructions in the documentation of the skeletons, so people will know what to do.

Structure of the file: Making it alphabetically sorted will just be confusing. Intead, using comments to divide it into sections. Each section will handle one tool or one kind of file. For example you could have these:

I can use files from existing projects as inspiration. gnome-common or mm-common may help provide a basis, but also check specific projects for the specific patterns they add.

UPDATE:

Skeleton’s .gitignore contains everything it needs at the moment, in order to build while ignoring all the generated files. Automation not necessary.

[See repo JSON]