Subj : exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
To   : Andre
From : deon
Date : Sun Apr 17 2022 10:30 am

  Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
  By: Andre to Digital Man on Sat Apr 16 2022 03:50 pm

 >  DM> Probably a new issue to be created whenever someone realizes/notices that a page is out of date. I do like to close issues with
 >  DM> commits to the source code, so I wouldn't want to change that work-flow.
 >
 > The only thing that made sense to me in my brief thinking about it is the manual creation of a new issue (in a separate project?),
 > since AFAIK there's no way to create an issue with a commit. Just website, email, url, etc.

While I havent explored it in detail - you (Rob) may be able to open an issue via an API call, when a commit is received (on master for example) - via a commit trigger?. And likewise, when a commit is done to the wikipages, it can auto close the issue if it's referenced in the commit message of the wiki update.

I can see it getting annoying though, because you'd probably want to suppress a document update (ie: issue creation) to some commits (eg: commits that fixes a bug but doesnt change functionality). That might be addressed by having commits needing a document update going to a particular branch before ending up on master.

Just spitballing here - I'm sure it's possible with automation but might be overly complex for a little BBS project...


....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!

.