Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is a bug? #643

Open
dabaus opened this issue Mar 11, 2025 · 0 comments
Open

What is a bug? #643

dabaus opened this issue Mar 11, 2025 · 0 comments

Comments

@dabaus
Copy link

dabaus commented Mar 11, 2025

So we had this discussion in our team that fix should basically only be used when there is a bug ticket. And because of that most people tend to use chore for everything except features and refactor, because
chore implies it's not a bug and low impact.

However, i think that anything that changes a feature in production should be regarded as a fix. And the reasoning behind it is that, even if it was the stakeholder that changed the specification, your application is no longer following the specification for this feature. Thus, you should make a fix for that.

Work-arounds for bugs in other systems, might also be a fix.

My take is that chore should only be used for configuration changes, adding stubs, new classes that are not yet in use , updating readme etc. Things that do not effect production in any way,

But i don't know. What do you think? What is the intention of fix? Do you think the intention is clear in the current document?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant