ratchetclank

I disagree, without this info, I can't easily tell if any commit is part of a feature or is a simple hotfix. I need to rely on the commiter to include the info in the commit message, which is almost always not the case.

I never understood why rebase is such a staple in the git world. For me "loosing" historical data, like on which branch my work was done is a real issue.

In the same class, for commit to not have on which branch they were created as a metadata is a rel painpoint. It always a mess to find what commit were done for what global feature/bugfix in a global gitflow process...

I'll probably be looking into adding an commit auto suffix message with the current branch in the text, but it will only work for me, not any contributors...

  Location: Luxembourg
  Remote: Hybrid or on-site
  Willing to relocate: No
  Technologies: Nutanix, VMWare, AD, Silverfort, Palo Alto, Fortigate, Cisco, Meraki, Windows, Linux, Azure, Powershell, Bash
  Résumé/CV: https://www.linkedin.com/in/remygrandin/
  Email: remy.gr@ndin.fr

I'm a system architect & administrator, specialized in virtualisation and network. I've work for 5+ years in a cybersecurity context while deploying numerous product internally.

In the same vibe I've been using https://darebee.com/ for quite a while. Good exercise library and great programs, all free for everyone.

We have been considering it in our team but the lack of capability of creating a "shared vault" and connecting it to a centralised AD/LDAP identity was a no go for us. Also, the lack, due to the tech itself, of a recovery method for users and administrator (with audit of course) was a big disapointment. PS : never connect it to your AD/ldap or it will spam everyone in your organisation by default ! #lessonlearned