Question: Good practice for this addin?

[hpollitte]

I am wondering the best way to utilize this add-in with git. While it does export the source file into a directory, what do you suggest as a good work-flow for utilizing GitHub in managing our MS Access project? We are new to github and are trying to find a way to get around the fact that MSAccess has no integrated git capabilities. Do you use work-trees for your branching?

Thank you.

[hecon5]

This is a complicated question; because it really depends much more on your git workflow. I can't speak for others, but our workflow morphed a good bit from when we first used it as we found what were "traditional best practices" needed to be tweaked for our environment and work flow.

We ended up using a dev-work-dev-stable approach. We branch off dev to add features/bug fixes, merge those back to dev, release as a beta to a smaller group, then if that works merge to stable. We rarely commit to stable directly; the only time we do is to do patch notes.

I use worktrees extensively myself, some of our other devs on the team don't like them, and don't. But for me, I find being able to have the "known stable" branch, "dev" branch, and the "I"m working on this" branch all live all the time when issues pop up; I just close one and open the other (this isn't required, but I get myself mixed up if I don't).

You can add a hook into MSAccess IIRC with the latest version of the Addin which will export after save (I've not done it, I like to push the "export" button myself for better control).

The latest version handles conflicts muuuuch better than it used to, so you could even do a 2-3 way merge (merge from your upstream/dev side to your work and export/import into MSAccess) at once, though that seems silly/dangerous.

My suggestion is to come up with some sort of plan, try it out and tweak it as you find better workflows. I've found the addin ties very nicely into git (it's basically the missing link between MSAccess and git, and is about the closest you'll find for natively integrated git tool as will get).

[hpollitte]

[like] Harrison Pollitte reacted to your message:

…

________________________________ From: hecon5 ***@***.***> Sent: Tuesday, June 11, 2024 1:08:43 PM To: joyfullservice/msaccess-vcs-addin ***@***.***> Cc: Harrison Pollitte ***@***.***>; Author ***@***.***> Subject: Re: [External] [joyfullservice/msaccess-vcs-addin] Question: Good practice for this addin? (Issue #514) This is a complicated question; because it really depends much more on your git workflow. I can't speak for others, but our workflow morphed a good bit from when we first used it as we found what were "traditional best practices" needed to be tweaked for our environment and work flow. We ended up using a dev-work-dev-stable approach. We branch off dev to add features/bug fixes, merge those back to dev, release as a beta to a smaller group, then if that works merge to stable. We rarely commit to stable directly; the only time we do is to do patch notes. I use worktrees extensively myself, some of our other devs on the team don't like them, and don't. But for me, I find being able to have the "known stable" branch, "dev" branch, and the "I"m working on this" branch all live all the time when issues pop up; I just close one and open the other (this isn't required, but I get myself mixed up if I don't). You can add a hook into MSAccess IIRC with the latest version of the Addin which will export after save (I've not done it, I like to push the "export" button myself for better control). The latest version handles conflicts muuuuch better than it used to, so you could even do a 2-3 way merge (merge from your upstream/dev side to your work and export/import into MSAccess) at once, though that seems silly/dangerous. My suggestion is to come up with some sort of plan, try it out and tweak it as you find better workflows. I've found the addin ties very nicely into git (it's basically the missing link between MSAccess and git, and is about the closest you'll find for natively integrated git tool as will get). — Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_joyfullservice_msaccess-2Dvcs-2Daddin_issues_514-23issuecomment-2D2160724949&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=egf7yPKrEdke2GWOidjlNxM3oh-4UdCJRE959ERWGdg&m=TBKWSNDsWmbM1JZqPgUkw3vHvRUfFiWXlJJdG1Du0OQgofT8HHYx0vmTtogGZtkI&s=GAoE6s9A7ewXTP0WKXmn6thvYuZaT_dzVbV-moPoIU8&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_BIWC774OGATJAECS4FKZY4LZG3ZFXAVCNFSM6AAAAABJC55F2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQG4ZDIOJUHE&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=egf7yPKrEdke2GWOidjlNxM3oh-4UdCJRE959ERWGdg&m=TBKWSNDsWmbM1JZqPgUkw3vHvRUfFiWXlJJdG1Du0OQgofT8HHYx0vmTtogGZtkI&s=lPK4FuYIct5PEJyxLjyhFst555jxKn8PvynqLn3bWQ4&e=>. You are receiving this because you authored the thread.Message ID: ***@***.***>

________________________________ This email has been scanned for spam and viruses by Proofpoint Essentials. Click here<https://us1.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f30b6043884178d3bb10e6c30ecd509c8c18aa1d43543ccdc78b8559ff1df8c3adbc26e46817afe6ee3c42a058f1563e84948ed6fa198daed5a398602fd820495ea500c949ba53ee50790d0a92899d1b7635b93f2818b70a3e7cc7c677b6fb01bd802382cdbaf587105a9bf2c2c10c42dca1df9f7e6ed19e1b999f5c0c3ff66cc346795ca9eb65d1f13fd22c7ddd88219020d84480167db3a> to report this email as spam.

[hecon5]

@hpollitte is this still an issue? If not, can you close it?