💾 Archived View for bbs.geminispace.org › s › Lagrange-Issues › 1 captured on 2023-12-28 at 17:19:48. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-14)
-=-=-=-=-=-=-
I should import all issues from the GitHub issue tracker and have them here. This'll ensure that the numbering of the existing issues matches what the repository is referring to.
Should also see if it's possible to close/archive the GitHub issues so new ones can't be posted there, otherwise there might be duplicate numering. Syncing GitHub with this Bubble subspace does not seem feasible/reasonable.
Will be interesting to see if this is actually workable for tracking bugs!
Existing issues already created here in Bubble will likely need to be renumbered when the GitHub issues are imported.
🐞 Issue #1 in s/Lagrange-Issues
May 13 · 8 months ago
🚀 skyjake · 2023-05-26 at 19:19:
I'm now syncing the Lagrange Git repository commits here. "BubbleID" is used for referencing issues in s/Lagrange-Issues.
🐞 Mentioned in [#38] Some nits re generated client certs
Jun 28 · 6 months ago
On second thought, maybe this won't be necessary. The GitHub tracker can live its own life.