You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feluda has multiple python packages in a single github repo, we could not find any existing tool/GitHub actions that can help us release and do semantic versioning of multiple packages in a monorepo. Hence we had to write our own custom script that does this for us. This is the GitHub action that trigger’s the workflow for semantic versioning - link. Wherever a PR is merged to main branch, this GitHub action is triggered.
Currently, whenever a change is made to feluda pacakge, a github release is made. But the CHANGELOG.md does not get updated.
The task of the issue is to modify the GitHub action to always update CHANGELOG.md along with the GitHub release. I have written some starter code for this - link.
The main challenge here is that, when using a custom markdown file as release notes, GitHub does not automatically include the list of contributors and alters the formatting of changes in the release notes.
Additionally, right now when a GitHub release is made just for feluda, all commits are present in the notes, how do we make sure only the commits that made changes to feluda/ folder i.e. the feluda python packages are only present
The text was updated successfully, but these errors were encountered:
Feluda has multiple python packages in a single github repo, we could not find any existing tool/GitHub actions that can help us release and do semantic versioning of multiple packages in a monorepo. Hence we had to write our own custom script that does this for us. This is the GitHub action that trigger’s the workflow for semantic versioning - link. Wherever a PR is merged to main branch, this GitHub action is triggered.
Currently, whenever a change is made to
feluda
pacakge, a github release is made. But theCHANGELOG.md
does not get updated.feluda/
folder i.e. the feluda python packages are only presentThe text was updated successfully, but these errors were encountered: