• 1 Post
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle
  • Interesting idea to store github comments inside git, the article just isn’t very clear to me on how to actually do it.

    He’s talking about using an “internal CLI tool” so I guess it’s not a public tool?

    But anyways, this kinda sounds like something you could do though a Github Action right? Like if a PR is merged, run an action that also appends PR comments or other meta-data from github into git







  • Well to be clear, this was not supposed to be a jab at gitflow, or me complaining specifically about gitflow. I merely used “gitflow” as an example of a set of conventions and standardizations that comes nicely packaged as one big set of conventions.

    But there’s nothing wrong with gitflow. I was just saying - it are not set in stone rules you must follow religiously. If you’re using it and it seems more practical to adapt the flow for your own use-case, don’t worry it’d be considered wrong to not stick strictly to it


  • I think a common misconception is that there’s a “right way to do git” - for example: “we must use Gitflow, that’s the way to do it”.

    There are no strict rules for how you should use git, it’s just a tool, with some guidelines what would probably work best in certain scenarios. And it’s fine diverge from those guidelines, add or remove some extra steps depending on what kinda project or team-structure you’re working in.

    If you’re new to Git, you probably shouldn’t just lookup Gitflow, structure your branches like that, and stick strictly to it. It’s gonna be a bit of trial-and-error and altering the flow to create a setup that works best