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
This script is copy-pasted for new projects, with a slight URL change so it generates the right commit URLs (as commit SHAs aren't auto-linked outside of issues, PRs and comments).
We should provide a simple command line program that essentially does this, but in not such a messy way. We should also change the configuration format from YAML to JSON (as we already have a JSON parser), and extend it to allow specifying a GitHub project URL, which would be used for generating links where necessary.
Since this would be an official Inko project, it would probably live at inko-lang/inko-changelog or something along those lines.
This will need a command line arguments parser first (similar to #597), and we'll need a basic Git client (using the git CLI, as libgit2 isn't great to work with, and doesn't support Git trailers anyway).
Given this is specific to Inko's GitHub workflow, and because I'm not quite sure yet about the specific details on how to implement this, this isn't something we'll be accepting contributions for, as I really want to think this through carefully.
The text was updated successfully, but these errors were encountered:
The script we use for generating changelogs is based on an API provided by GitLab, also written by yours truly.
This script is copy-pasted for new projects, with a slight URL change so it generates the right commit URLs (as commit SHAs aren't auto-linked outside of issues, PRs and comments).
We should provide a simple command line program that essentially does this, but in not such a messy way. We should also change the configuration format from YAML to JSON (as we already have a JSON parser), and extend it to allow specifying a GitHub project URL, which would be used for generating links where necessary.
Since this would be an official Inko project, it would probably live at inko-lang/inko-changelog or something along those lines.
This will need a command line arguments parser first (similar to #597), and we'll need a basic Git client (using the
git
CLI, as libgit2 isn't great to work with, and doesn't support Git trailers anyway).Given this is specific to Inko's GitHub workflow, and because I'm not quite sure yet about the specific details on how to implement this, this isn't something we'll be accepting contributions for, as I really want to think this through carefully.
The text was updated successfully, but these errors were encountered: