[#1] Import issues from GitHub?

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
=> 🕹ī¸ skyjake [mod, sysop]

2023-05-13 ¡ 2 years ago

2 Comments ↓

=> 🕹ī¸ skyjake [OP/mod...] ¡ 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

2023-06-28 ¡ 2 years ago

=> 🕹ī¸ skyjake [OP/mod...] ¡ 2023-10-25 at 14:53:

On second thought, maybe this won't be necessary. The GitHub tracker can live its own life.

Proxy Information
Original URL
gemini://bbs.geminispace.org/s/Lagrange-Issues/2
Status Code
Success (20)
Meta
text/gemini; charset=utf-8
Capsule Response Time
68.525939 milliseconds
Gemini-to-HTML Time
0.849907 milliseconds

This content has been proxied by September (3851b).