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
It has become too cumbersome to find the issue number when committing some changes about a language kernel. I think this adds significant mental overheads now as we have dozens of language kernels with irregularly ordered issue numbers.
So I'd like to make a little more room for flexibility of issue references. Let's just use a simple prefix like "python: ", "rust: ", etc. when committing changes about a specific language kernel.
Of course, still we should use explicit issue numbers for bugs and new feature sets.
There is no clear-cut rule when to use numbers or prefixes – you may even mix them – but let's have two key principles:
Make the changes recorded and searchable afterwards.
Git itself is the best tool to record changes with good commit messages and atomic commits.
For the record of history, here I gathered all lang-related issues:
It has become too cumbersome to find the issue number when committing some changes about a language kernel. I think this adds significant mental overheads now as we have dozens of language kernels with irregularly ordered issue numbers.
So I'd like to make a little more room for flexibility of issue references. Let's just use a simple prefix like "python: ", "rust: ", etc. when committing changes about a specific language kernel.
Of course, still we should use explicit issue numbers for bugs and new feature sets.
There is no clear-cut rule when to use numbers or prefixes – you may even mix them – but let's have two key principles:
For the record of history, here I gathered all lang-related issues:
I left a few issues about languages that are NOT implemented yet, though.
The text was updated successfully, but these errors were encountered: