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
When #8 is done, users will get confused since there are two similar commands: kata version and kata versions, deprecate kata versions (make new command for this but don't delete it yet, since some users might still use it), rename it to something more useful i.e. kata bot-versions.
The text was updated successfully, but these errors were encountered:
I would still like something better than kata versions since it's ambiguous and the purpose of the command could be made clearer by giving better "nouns". But not that urgent for now, any thoughts? I made a bunch of new labels for priority, we can make use of it, I'm giving this important-longterm. Also in the future I'm thinking to track all issues related to everything (public/community will start reporting issues/feature request etc once adopted) in a single repo here along with bot examples (https://github.com/kata-ai/bot-samples), will need to rename the repo to /community or something. Inspired by https://github.com/meya-ai/community
I see, agreed with /community ideas, if people want to solve issue and then doing pull request, are they still pr to associate repo (e.g. kata-cli) or how ?
When #8 is done, users will get confused since there are two similar commands:
kata version
andkata versions
, deprecatekata versions
(make new command for this but don't delete it yet, since some users might still use it), rename it to something more useful i.e.kata bot-versions
.The text was updated successfully, but these errors were encountered: