#gitignore — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitignore, aggregated by home.social.
-
Gunakan template .gitignore standar ini untuk project Node.js agar folder seperti node_modules, .npm-cache, file log, dan .env tidak ikut ter-commit ke Git.
-
:git: #TIL Put the line
**/*__gitignore__*
in your ~/.gitignore_global file to ignore any file or directory whose name contains __gitignore__ anywhere in the path.
This handy little glob trick allows you to quickly create a space for temporary files, ad-hoc-experiments or other "stuff" you want to keep out of version control (and also out of you versioned repo-specific .gitignore)
-
Гит в Телеграм?
На своем тг-канале я предлагаю подписчикам выбор, какую бредовую идею запилить следующей. На этот раз подписчики выбрали новый челлендж: сделать Git в Telegram. Чтобы можно было через бота инитить проекты, пушить файлы, коммитить — и всё это в публичном канале с тредами. С практической точки зрения этот проект на хуй не нужен. Есть гитхаб, есть гитлаб, есть куча нормальных инструментов. Но как эксперимент — почему бы и нет? Чисто посмотреть, можно ли заставить Telegram работать как VCS. Я тогда подумал: «Ну, бот на aiogram, база данных, пара команд — делов то))» Словари, датаклассы и прочая е*атория Когда я только начинал, первая мысль была: «Положу всё в JSON, на кой мне база данных?» Ну серьёзно, проектов мало, пользователей немного, файлы текстовые че заморачитватся. Подергал JSON туда-сюда пару дней и понял: не варик. Во-первых, конкурентный доступ. Два юзера одновременно коммитят — один из них перезаписывает файл другого. Во-вторых, целостность данных. Если бот упал в середине записи — JSON остаётся в невалидном состоянии. В-третьих, версионность. Хранить историю изменений в JSON — это просто перенести проблему из кода в структуру файла. Короче, JSON — для конфигов, а не для данных, которые меняются каждую секунду. Выбор пал на SQLite. Почему:
https://habr.com/ru/articles/1008202/
#Telegram_бот #Git #Python #aiogram #SQLite #git_в_telegram #gitignore
-
Found a .gitignore helper for the terminal! 🔥
🌀 **autogitignore** — A TUI for searching, previewing & generating .gitignore files
💯 Fuzzy search, multi-template selection, offline cache & safe writes with backup
🦀 Written in Rust & built with @ratatui_rs
⭐ GitHub: https://github.com/Bilal-AKAG/autogitignore
#rustlang #ratatui #tui #git #gitignore #cli #devtools #opensource
-
Als #Entwickler arbeitet man ja meist in Repositories und nicht alle #Dateien in diesen Verzeichnissen sollen oder dürfen in das #Repository rein (Credentials, Notizen, KI-Dateien).
Und manche von diesen Dateien will man aber dennoch archiviert oder versioniert haben.
Ich glaube, ich hab dafür eine richtig gute Lösung gefunden, die ich die nächsten Tage ausgiebig testen und danach veröffentlichen werde
-
Als #Entwickler arbeitet man ja meist in Repositories und nicht alle #Dateien in diesen Verzeichnissen sollen oder dürfen in das #Repository rein (Credentials, Notizen, KI-Dateien).
Und manche von diesen Dateien will man aber dennoch archiviert oder versioniert haben.
Ich glaube, ich hab dafür eine richtig gute Lösung gefunden, die ich die nächsten Tage ausgiebig testen und danach veröffentlichen werde
-
Als #Entwickler arbeitet man ja meist in Repositories und nicht alle #Dateien in diesen Verzeichnissen sollen oder dürfen in das #Repository rein (Credentials, Notizen, KI-Dateien).
Und manche von diesen Dateien will man aber dennoch archiviert oder versioniert haben.
Ich glaube, ich hab dafür eine richtig gute Lösung gefunden, die ich die nächsten Tage ausgiebig testen und danach veröffentlichen werde
-
Als #Entwickler arbeitet man ja meist in Repositories und nicht alle #Dateien in diesen Verzeichnissen sollen oder dürfen in das #Repository rein (Credentials, Notizen, KI-Dateien).
Und manche von diesen Dateien will man aber dennoch archiviert oder versioniert haben.
Ich glaube, ich hab dafür eine richtig gute Lösung gefunden, die ich die nächsten Tage ausgiebig testen und danach veröffentlichen werde
-
Als #Entwickler arbeitet man ja meist in Repositories und nicht alle #Dateien in diesen Verzeichnissen sollen oder dürfen in das #Repository rein (Credentials, Notizen, KI-Dateien).
Und manche von diesen Dateien will man aber dennoch archiviert oder versioniert haben.
Ich glaube, ich hab dafür eine richtig gute Lösung gefunden, die ich die nächsten Tage ausgiebig testen und danach veröffentlichen werde
-
Gunakan template .gitignore standar ini untuk project Node.js agar folder seperti node_modules, .npm-cache, file log, dan .env tidak ikut ter-commit ke Git.
-
AI Agent “Security” in One Screenshot
https://kerrick.blog/posts/2025/ai-agent-security-in-one-screenshot/
-
AI Agent “Security” in One Screenshot
https://kerrick.blog/posts/2025/ai-agent-security-in-one-screenshot/
-
AI Agent “Security” in One Screenshot
https://kerrick.blog/posts/2025/ai-agent-security-in-one-screenshot/
-
AI Agent “Security” in One Screenshot
https://kerrick.blog/posts/2025/ai-agent-security-in-one-screenshot/
-
AI Agent “Security” in One Screenshot
https://kerrick.blog/posts/2025/ai-agent-security-in-one-screenshot/
-
TIL: gitignore.io ist unmaintained. Die Firma, die das aufgekauft(?) hat, hat große Teile der Quellcodes auf github gelöscht und die Templates werden wohl nicht mehr Aktualisiert. Gibt wohl Versuche ne Alternative zu schaffen, z.B. donotcommit.com, sehen bisher aber auch eher unfertig aus :/
#git #github #gitignore -
I was getting wound up yesterday as I wanted to create a gitignore file and I couldn't be bothered to leave the terminal. So I created Snub (it's like ignoring, but with attitude) to scratch an itch.
The code is up on codeberg along with a first release. There's a few things I want to add to it still, but thought I'd share in case it's useful for anyone.
-
Харденинг GitLab: хитрость лисы в защите кода организации
Привет, Хабр! Я Антон Ерёмин, ведущий инженер дирекции инфраструктурных проектов Positive Technologies. Сегодня на примере харденинга реальных сервисов продолжаем рассказывать о нашей методологии ХардкорИТ — подходе к определению времени атаки и вероятных маршрутов хакеров. В прошлый раз мы проводили харденинг инфраструктуры Microsoft Exchange, затрудняя возможность ее атаки, разбирались в тонкостях защиты zVirt. Теперь настало время рассказать про харденинг GitLab.
https://habr.com/ru/companies/pt/articles/886708/
#gitlab #безопасность #cybersecurity #devops #devsecops #gitignore #gitconfig #ci #cd
-
Today I found a TUI that helps with .gitignore files! 🔥
🧩 **gitnr**: Create .gitignore files using one or more templates.
🚀 Search and select templates & filter out duplicate lines.
🦀 Written in Rust & built with @ratatui_rs
⭐ GitHub: https://github.com/reemus-dev/gitnr
#rustlang #ratatui #tui #git #gitignore #templates #generator #commandline #terminal #tool
-
Someone made a PR to add .DS_Store to the .gitignore file in the Linux kernel repository.
Anyway best tip 🤯
#git #gitignore #linux #macos -
Как работать с Git и Gitflow: разбираемся на примерах
Привет, Хабр! Меня зовут Николай Пискунов, я руководитель направления Big Data и в блоге
https://habr.com/ru/companies/beeline_cloud/articles/829142/
-
Hey #Eleventy tinkerers!
I have a git submodule that I am adding inside the repository of my website, but I want it to be ignored, except for its
README.md.I have tried two different approaches. In both cases I am able to exclude the git submodule, but I can’t find a way to include the README and use it as a regular template.
Option 1: using
.eleventyignoreinputdir/submodule
!inputdir/submodule/README.mdOption 2: using
.eleventy.jsmodule.exports = function (eleventyConfig) {
eleventyConfig.ignores.add('inputdir/submodule');
eleventyConfig.ignores.add('inputdir/submodule/README.md'); // added it first to be sure
eleventyConfig.ignores.delete('inputdir/submodule/README.md');
};Do you have any suggestions to fix this? The ignore section in Eleventy’s documentation is not helping much…
Thanks a lot!
#11ty #help #WebDev #JavaScript #gitignore
cc: @eleventy @
-
Mastering Python packages: organizing files and best practices - Virtual environments (#02)
-
CW: Apparently I don't actually understand .gitignore syntax.
(...and apparently CWs render HTML as plaintext, so: .gitignore syntax)
What I want is to exclude any folder that has "RETIRED" in the name -- even if it's prefixed (I sometimes stick a "0 " at the beginning so it will sort to the top rather than being in the middle of the other, active folders).
Any of these lines will exclude any folder that is named exactly "RETIRED":
/*RETIRED/*RETIRED//*RETIRED/**/**RETIRED//0?RETIRED/0?RETIRED/So far so good... except none of these will exclude folders named "0 RETIRED", which they all kind of seem like they ought to do.
I've also tried the following:
*RETIRED**/*RETIRED...but neither of them exclude anything.
What am I doing wrong? Is the documentation even correct?
-
https://dev.to/fronkan/a-personal-gitignore-even-for-a-single-repository-4o7h - want to exclude more from #git than what's in #gitignore? There's a few options: 1. global .gitignore, 2. change local git to use different ignore file, 3. .git/info/exclude. Great list of pros & cons for each https://github.com/Fronkan.
-
Today I wrote some trivial #python code to convert .gitignore rules to #radon exclude/ignore patterns. It turns out it was completely unnecessary for our project (#wily), because we already pass a tight list of targets for radon to scan.
But it might be useful for upstream radon users, as an option to gather exclude/ignore rules from .gitignore. So I'll propose that as a new feature and see how it goes.
-
Today I wrote some trivial #python code to convert .gitignore rules to #radon exclude/ignore patterns. It turns out it was completely unnecessary for our project (#wily), because we already pass a tight list of targets for radon to scan.
But it might be useful for upstream radon users, as an option to gather exclude/ignore rules from .gitignore. So I'll propose that as a new feature and see how it goes.
-
Today I wrote some trivial #python code to convert .gitignore rules to #radon exclude/ignore patterns. It turns out it was completely unnecessary for our project (#wily), because we already pass a tight list of targets for radon to scan.
But it might be useful for upstream radon users, as an option to gather exclude/ignore rules from .gitignore. So I'll propose that as a new feature and see how it goes.
-
Today I wrote some trivial #python code to convert .gitignore rules to #radon exclude/ignore patterns. It turns out it was completely unnecessary for our project (#wily), because we already pass a tight list of targets for radon to scan.
But it might be useful for upstream radon users, as an option to gather exclude/ignore rules from .gitignore. So I'll propose that as a new feature and see how it goes.
-
Today I wrote some trivial #python code to convert .gitignore rules to #radon exclude/ignore patterns. It turns out it was completely unnecessary for our project (#wily), because we already pass a tight list of targets for radon to scan.
But it might be useful for upstream radon users, as an option to gather exclude/ignore rules from .gitignore. So I'll propose that as a new feature and see how it goes.
-
Esta extensión para Visual Studio Code me parece un MUST: https://marketplace.visualstudio.com/items?itemName=codezombiech.gitignore no solo puedes añadir el gitignore que necesitas para tu proyecto sino que te permite hacer una actualización del mismo si añades otros tipos que lo complementan #vscode #gitignore #git
-
Am heutigen #toolsday wollen wir euch ein online Dienst zur Erstellung von gitignore Dateien vorstellen. Wer von euch heufig #git Projekte anlegt, freut sich sicher über ein wenig nützliche Hilfe bei der Erzeugung der #gitignore. Mit gitignore.io gehosted von toptal lassen sich via API oder auf der Webseite gitignoredateien speziell für die eigene Projekte erzeugen. Dabei werden Programmiersprachen, Template und vieles mehr sprachen zur auswahl angeboten. https://github.com/toptal/gitignore.io
-
Controversial take on #GitIgnore: don't put editor backup files in a #repository's .gitignore, your editor is your choice so others don't need to know about it: Put it in $XDG_CONFIG_HOME/git/ignore instead (or somewhere you set with core.excludesFile).
This also reduces my need to set up a .gitignore for every new repository, or throw in long automatically generated files with excludes for every editor that exists.
Reply includes my own ignore patterns. #git 1/2
-
Little remind: Setting up a global .gitignore file
« My repository doesn’t care about your editor configuration. »
https://sebastiandedeyne.com/setting-up-a-global-gitignore-file/
-
#Gitignore Generator using #GitHub's gitignore files