Closed francislavoie closed 4 months ago
+1 for the releases. It would be nice to use these new changes. 😃
Unfortunately, I'm still figuring out how releases were done in the original repo. He didn't use github actions, so there's only fragments of what he was doing previously copied over in the fork.
So I'm in the process of figuring out how to use github actions to do static code analysis, automate releases, etc. Once it's working, releases should be published automatically as a side-effect of tagging the repo, along with a changelog.
New territory for me; I'm usually doing embedded Linux development using an entirely different build system and continuous integration pipeline. Please bear with me; lots of new stuff to learn.
@hugbug would you be willing to provide some insight on how you used to make the releases? It would help make the transition easier!
I've made an attempt to update the URLs. See also: https://github.com/nzbget-ng/nzbget-ng.github.io/pull/2
Thanks for everything @paul-chambers !
I'm glad to see this get forked, and I hope this continues to be maintained! I love NZBGet, and I just found out the original repo was archived, which makes me sad.
I noticed that there's no Releases tab yet, and there's no builds with the changes since forking. I figured I'd open this issue to keep track of that. https://nzbget-ng.github.io/download will also need to be updated with those releases, which is sourced from the file here https://github.com/nzbget-ng/nzbget-ng.github.io/blob/trunk/_data/version.json