Skip to content

Conversation

@sageserpent-open
Copy link
Contributor

Added entries for easy watching, Git tools and sites and releases.

@chriscool
Copy link
Collaborator

chriscool commented Sep 2, 2025

@sageserpent-open thanks for the contribution. Next times it would be better if your contributions can be made earlier, so we have more time to process them before publishing the edition.

@jnareb do you have time to look at this? I will take care of the change in the "Releases" section separately.

@chriscool
Copy link
Collaborator

Added the release in: 1d5998d

@chriscool
Copy link
Collaborator

chriscool commented Sep 2, 2025

By the way, @sageserpent-open, the "Releases" section is mostly automatically generated by this script:

https://github.com/chriscool/getreleases/blob/master/get_releases.py

feel free to contribute to it, so that new Kinetic Merge releases are automatically generated by the script for new Git Rev News editions. It will likely require no more than a few lines of code. Let me know if you need help for this.

@sageserpent-open
Copy link
Contributor Author

By the way, @sageserpent-open, the "Releases" section is mostly automatically generated by this script:

https://github.com/chriscool/getreleases/blob/master/get_releases.py

feel free to contribute to it, so that new Kinetic Merge releases are automatically generated by the script for new Git Rev News editions. It will likely require no more than a few lines of code. Let me know if you need help for this.

I'll do that, it looks straightforward enough but I'd like to experiment on my machine to make sure I understand precisely what the regex scraping is doing wrt what comes out of the GitHub release API.

I'll raise a PR in a few days (won't be able to get to a development machine tomorrow).

Many thanks for looking into this, @chriscool and @jnareb .

@chriscool
Copy link
Collaborator

@sageserpent-open, unfortunately @jnareb has not replied yet and I have to publish edition 126 this evening. Also the changes to the "Other News" section are relatively big, so I would prefer not to make them without his approval.

Let's postpone this MR for the next edition then. I just created the issue for the next edition and left a comment about this MR so we don't forget.

Thanks for your understanding!

@sageserpent-open
Copy link
Contributor Author

@chriscool No problem, everyone is busy. I shall resubmit for the next issue. Thanks again for your consideration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants