> When browsing issues on GitHub I have often been confused about their
> status.
new -> is:open no:assignee
ongoing -> is:open assignee:*
blocked -> anyone really filtering for that?
duplicate -> [1]
worksforme -> simply close it with a comment
invalid -> simply close it with a comment
fixed -> [2] then is:closed linked:pr
There is much more to discover:
https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests
[1]
https://docs.github.com/en/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate
[2] https://github.blog/2013-01-22-closing-issues-via-commit-messages/
Am 28.04.22 um 21:53 schrieb Jens Lideström:
One convenient detail in Bugzilla is that there is a "Status" field on
every issue. The status is explicit, has standardized values and is
immediately visible.
When browsing issues on GitHub I have often been confused about their
status.
I suggest this: All Eclipse projects on GitHub should have labels for
the most important status values that exist in Bugzilla.
Maybe the following status values should exist:
new
ongoing
blocked
duplicate
worksforme
invalid
fixed
It would be preferable if one of the status labels would be mandatory
for a issue to be closed, but I don't know if GitHub has functionality
for that.
Bugzilla status values:
https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_status
Labels for an organisation in GitHub:
https://docs.github.com/en/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization
BR,
Jens Lideström
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
