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
Is your feature request related to a problem? Please describe.
There is actually no problem. Every OpenSource project use (at least) git tags and/or Github Releases to publish new semantic versions.
Describe the feature you'd like
It's not a feature, but a request to know what is the developpment workflow around QB-Core, how do things are versionned, document the way that features are implemented. And redirect issues to proper resources (there is a lot of resources and we can easily get lost in it)
Releases are a safest way to notify users of a stable version (with Github bot to check CodeStyle, luacheck etc...)
You can easily add SQL Migrations so people doesn't need to drop Database and reimport datas after migration.
Describe alternatives you've considered
I can try to write my own Documentation about how does QB-Core team works with GitHub and how to contribute. But I'm pretty knew and I don't understand the whole process (or I didn't found the resources about it)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There is actually no problem. Every OpenSource project use (at least) git tags and/or Github Releases to publish new semantic versions.
Describe the feature you'd like
It's not a feature, but a request to know what is the developpment workflow around QB-Core, how do things are versionned, document the way that features are implemented. And redirect issues to proper resources (there is a lot of resources and we can easily get lost in it)
Releases are a safest way to notify users of a stable version (with Github bot to check CodeStyle, luacheck etc...)
You can easily add SQL Migrations so people doesn't need to drop Database and reimport datas after migration.
Describe alternatives you've considered
I can try to write my own Documentation about how does QB-Core team works with GitHub and how to contribute. But I'm pretty knew and I don't understand the whole process (or I didn't found the resources about it)
The text was updated successfully, but these errors were encountered: