automating changelogs, git workflows
so i wanted to get advice on both topics
automating changelogs
How do ya'll usually deal with this? I specifically want to automate/semi-automate changelogs for our users/client to see. We/I already use semantic commits.
For the documentation tool itself, found out about fumadocs, but the automating of changelogs part is something im not sure how to go about
git workflows
I have a bit of confusion about this. For background, im looking for a relatively simple git workflow.
I used to do something like having a main and a dev (which i use as a staging environment) and i branch off of dev to create feature branches, merge them back to dev, do some automated and manual testing on the dev/staging environment before merging back to main.
However, ive recently come across TBD which seems to espouse short-lived feature branches and directly branching off main, which I liked for how simple it is and minimizes merge conflicts.
However, it seems like the new complexity that arises with this is that this will require preview deployment links in place of a staging environment, which is all fine and all since coolify has this (I don't use vercel/netlify).
But one major PITA that I've found with this workflow is having to rework my authentication to work with dynamically-generated preview links (in particular google's authorized and callback URIs).
So I'd like to get some advice on this as well
(3). some sort of ai tool for automating/syncing documentation with code
ya'll have any suggestions for this? keeping code documentation in sync with the actual code is kinda a PITA. there's coderabbit, cursor bugbot but those are heavily tailored for code reviews afaik
Stack: React + Typescript, Coolify/VPS
automating changelogs
How do ya'll usually deal with this? I specifically want to automate/semi-automate changelogs for our users/client to see. We/I already use semantic commits.
For the documentation tool itself, found out about fumadocs, but the automating of changelogs part is something im not sure how to go about
git workflows
I have a bit of confusion about this. For background, im looking for a relatively simple git workflow.
I used to do something like having a main and a dev (which i use as a staging environment) and i branch off of dev to create feature branches, merge them back to dev, do some automated and manual testing on the dev/staging environment before merging back to main.
However, ive recently come across TBD which seems to espouse short-lived feature branches and directly branching off main, which I liked for how simple it is and minimizes merge conflicts.
However, it seems like the new complexity that arises with this is that this will require preview deployment links in place of a staging environment, which is all fine and all since coolify has this (I don't use vercel/netlify).
But one major PITA that I've found with this workflow is having to rework my authentication to work with dynamically-generated preview links (in particular google's authorized and callback URIs).
So I'd like to get some advice on this as well
(3). some sort of ai tool for automating/syncing documentation with code
ya'll have any suggestions for this? keeping code documentation in sync with the actual code is kinda a PITA. there's coderabbit, cursor bugbot but those are heavily tailored for code reviews afaik
Stack: React + Typescript, Coolify/VPS
