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
I've searched existing issues and found nothing related to my issue.
Describe the feature you want to add
First of all, I want to say that this product is great and say thanks for that @helloanoop .
If the plan is to mantain it opensource and accept contributions I suggest to homogenize rules of issues and PRs
Template for PRs ask us to link one existent issue or create a new one. In general, issues and PRs open by the comunity are linked that way. This allow to set the a scope and understand the evolution of the product.
In last release: 1.38 all changes were made by internal team, no all PRs had an issue related, some were linked to your internal Jira, and some of PRs have with no further explainantion, . May be some titles are easy to understand but others are very cryptic and there is no context.
It is helpful for contributors keeping quality documentation.
Mockups or Images of the feature
N/A
The text was updated successfully, but these errors were encountered:
Hi @tlaloc911, we understand the concern. We do have a template in place for the PRs which asks the devs to link to an issue and add a good description but I see some have missed to add that. My apologies for that. We will work on this and get this working from the next releases. Thank you for your understanding!
I have checked the following:
Describe the feature you want to add
First of all, I want to say that this product is great and say thanks for that @helloanoop .
If the plan is to mantain it opensource and accept contributions I suggest to homogenize rules of issues and PRs
Template for PRs ask us to link one existent issue or create a new one. In general, issues and PRs open by the comunity are linked that way. This allow to set the a scope and understand the evolution of the product.
In last release: 1.38 all changes were made by internal team, no all PRs had an issue related, some were linked to your internal Jira, and some of PRs have with no further explainantion, . May be some titles are easy to understand but others are very cryptic and there is no context.
It is helpful for contributors keeping quality documentation.
Mockups or Images of the feature
N/A
The text was updated successfully, but these errors were encountered: