[GH-ISSUE #46] Better CI, dev branch, git flow #4

New issue

Closed

opened 2026-10-13 19:45:27 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 19:45:27 +00:00

Owner

Originally created by @Glitchy-Sheep on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/Glitchy-Sheep/boosty-downloader/issues/46

Originally assigned to: @Glitchy-Sheep on GitHub.

The problem

Now the project lacks automatic CI testings/linting and in general should have a better rule for release cycle.

The solution

Add a dev branch for ongoing development, updates, and Renovate-related activity.
Configure CI to run on all pull requests:
- Tests (unit/integration)
- Linters
- Some version checking
Add a CONTRIBUTING.md file and basic contribution guidelines/documentation.

Originally created by @Glitchy-Sheep on GitHub (Jul 27, 2025). Original GitHub issue: https://github.com/Glitchy-Sheep/boosty-downloader/issues/46 Originally assigned to: @Glitchy-Sheep on GitHub. # The problem Now the project lacks automatic CI testings/linting and in general should have a better rule for release cycle. # The solution - Add a dev branch for ongoing development, updates, and Renovate-related activity. - Configure CI to run on all pull requests: - Tests (unit/integration) - Linters - Some version checking - Add a CONTRIBUTING.md file and basic contribution guidelines/documentation.

bsakaguchi

2026-10-13 19:45:27 +00:00