VirtualTam's bookmarks

201. Google Open Source Blog: Bidding farewell to Google Code 2015-03-15

     tags: closed, code, development, google, source-code-management/git, source-code-management/github

     [ permalink ]

     TL;DR

     • March 12, 2015 - New project creation disabled.
     • August 24, 2015 - The site goes read-only.
     • January 25, 2016 - The project hosting service is closed.
202. Git - Submodules 2015-03-15

     tags: control, multiple, repository, source-code-management/git, submodule, version

     [ permalink ]

     • https://github.com/git/git/blob/master/git-submodule.sh
     • https://github.com/git/git/blob/master/submodule.c
     • https://github.com/git/git/blob/master/submodule.h
203. Creating a custom git flow visualization 2015-03-02

     tags: control, development, flow, source-code-management/git, stash, version

     [ permalink ]
204. A successful Git branching model 2015-03-02

     tags: branch, control, development, management, release, source-code-management/git, version

     [ permalink ]
205. How would git handle a SHA-1 collision on a blob? - Stack Overflow 2015-02-14

     tags: algorithm, code, collision, commit, cryptography/hash, patch, review, security, sha1, source-code-management/gerrit, source-code-management/git

     [ permalink ]

     • https://en.wikipedia.org/wiki/SHA-1
     • http://stackoverflow.com/questions/1867191/probability-of-sha1-collisions
     • http://en.wikipedia.org/wiki/Birthday_problem

     Some thoughts we had while toying with Gerrit, which artificially tracks different commits to group them as "patch sets", by using a Change-Id SHA-1 in the commit message:

     • https://gerrit-review.googlesource.com/Documentation/cmd-hook-commit-msg.html
     • https://gerrit.googlesource.com/git-repo/+/master/hooks/commit-msg
206. gitbrute: bruteforce a Git commit SHA-1 2015-02-14

     tags: collision, commit, cryptography/hash, sha1, source-code-management/git

     [ permalink ]

     Applied example: https://github.com/bradfitz/deadbeef

207. [aur-dev] AUR 4.0.0 pre-alpha 2015-01-06

     tags: aur, linux, linux/archlinux, package, source-code-management/git

     [ permalink ]

     Git is coming to AUR (or, AUR is coming to Git?)

208. Git pretty: time to tidy your versioning mess! 2014-12-16

     tags: branch, commit, control, development, history, source-code-management/git, version

     [ permalink ]

     How to solve Git issues...

     from https://presentate.com/bobthecow/talks/changing-history

209. github - Delete a Git branch both locally and remotely - Stack Overflow 2014-12-08

     tags: branch, delete, remote, source-code-management/git, source-code-management/github

     [ permalink ]
210. Github issue etiquette 2014-12-04

     tags: agile, community, feedback, issue, source-code-management/git, source-code-management/github, tracker

     [ permalink ]
211. Diffuse - Portable merge tool 2014-12-04

     tags: control, file, merge, revision, source-code-management/git, source-code-management/subversion, version

     [ permalink ]
212. GitLab, mais encore ? - LinuxFr.org 2014-12-02

     tags: code, control, development, gitorious, gogs, source-code-management/git, source-code-management/gitlab, version, web

     [ permalink ]

     Discussion de fond sur l'auto-hébergement de code source via Git :

     • mise en place d'une interface d'administration web,
     • fonctionnalités couvertes : granularité des droits, CI, wiki,
     • simplicité d'utilisation,
     • réactivité,
     • interactivité avec la communauté / cadre d'utilisation.
213. Gogs: Go Git Service - A self-hosted Git service written in Go 2014-12-02

     tags: code, development, server, source-code-management/git, web

     [ permalink ]
214. Notre workflow git, pourquoi, comment 2014-12-02

     tags: branch, continuous-integration, development, source-code-management/git, workflow

     [ permalink ]

     via http://linuxfr.org/users/crev/journaux/git-workflow-rebase-conflits-et-role-d-integrateur

215. Continuous integration in Python 2014-11-27

     tags: automation, continuous-integration, continuous-integration/travis, development, programming/python, programming/python/pytest, programming/testing, source-code-management/git, unit

     [ permalink ]

     http://ilovesymposia.com/2014/10/01/continuous-integration-0-automated-tests-with-pytest/ http://ilovesymposia.com/2014/10/02/continuous-integration-1-test-coverage/ http://ilovesymposia.com/2014/10/13/continuous-integration-in-python-3-set-up-your-test-configuration-files/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-4-set-up-travis-ci/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-5-report-test-coverage-using-coveralls/ http://ilovesymposia.com/2014/10/17/continuous-integration-in-python-6-show-off-your-work/ http://ilovesymposia.com/2014/10/27/continuous-integration-in-python-7-some-helper-tools-and-final-thoughts/

216. gource - software version control visualization 2014-11-26

     tags: agile, commit, continuous-integration, development, game/minecraft, linux, observability/logging, programming/python, project, software, source-code-management/git, source-code-management/subversion, user, version

     [ permalink ]

     Uses a project or repository's history to plot user contributions, displaying an elegant, colored graph of the file arborescence.

     After running it on quite different projects...

     • Python/Bash CI/Jenkins scripts
     • Qt apps: GoldenDict, Psi+
     • PHP website: Shaarli

     ...watching some vids on teh intartubez:

     • Minecraft: https://www.youtube.com/watch?v=zRjTyRly5WA
     • Linux kernel: https://www.youtube.com/watch?v=AhDiYPLo3p4
     • Python: https://www.youtube.com/watch?v=cNBtDstOTmA

     It allows to arbitrary spot some interesting implementation aspects (sorted by descending impact):

     • language-dependent trees (oh hai Java packages ^^)
     • framework-dependent trees
     • project-management method (none, Agile, TDD)

     Having a graphical tool also quickly shows:

     • the overall structure of the project (a bit cooler than a simple $ tree, way quicker than loading the project on an IDE)
     • the repartition of files (by extensions)
     • who are the most active contributors
     • what are the most modified files over time
     • who does what: additions, deletions, refactoring

     Some more CI-related matters:

     • are there any tests?
     • what is the source code / test code ratio? (we could expect a project/lib with N modules to have at least N test modules)
     • who initiates / implements / optimizes test code?
217. Github Badge Service 2014-11-23

     tags: badge, continuous-integration, service, source-code-management/git, status

     [ permalink ]
218. paigeadele - HydrogenTracks 2014-11-04

     tags: beats, digital-audio-workstation, hydrogen, instrument/drums, linux, source-code-management/github, tracks

     [ permalink ]

     Cool!

219. Git cheat sheet 2014-11-02

     tags: control, reference, source-code-management/git, version

     [ permalink ]
220. Commit Logs From Last Night 2014-10-23

     tags: code, commit, development, drunk, observability/logging, source-code-management/git, wtf

     [ permalink ]

     Tu t'es débuggé quand t'as bu ‽