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

feat(issues-list): add tag 'new' #927

Merged
merged 2 commits into from
Feb 14, 2025
Merged

feat(issues-list): add tag 'new' #927

merged 2 commits into from
Feb 14, 2025

Conversation

murilx
Copy link
Contributor

@murilx murilx commented Feb 13, 2025

  • Changed the issuesExtra response to include more info about the first incident of each issue, including commit hash, git branch and git url
  • Added the pill to the issue list if the commit hash of the first incident is the same commit hash of the tree details page

Closes #571

How to test

You can verify if an issue is really new if when you open its issue details there's only one test/build

Visual reference

http://localhost:5173/tree/f5d74f9f7c3b2495596b43c01f5747b66c8ef70d?ti%7Cc=v6.9-12136-gf5d74f9f7c3b&ti%7Cch=f5d74f9f7c3b2495596b43c01f5747b66c8ef70d&ti%7Cgb=nvme-rx-offload-v25&ti%7Cgu=https%3A%2F%2Fgithub.com%2Faaptel%2Flinux.git&ti%7Ct=aaptel
image

http://localhost:5173/tree/4dc1d1bec89864d8076e5ab314f86f46442bfb02?iv=1&p=bt&ti%7Cc=v6.14-rc2-41-g4dc1d1bec8986&ti%7Cch=4dc1d1bec89864d8076e5ab314f86f46442bfb02&ti%7Cgb=master&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&ti%7Ct=mainline
image

@murilx murilx self-assigned this Feb 13, 2025
@murilx murilx force-pushed the feat/new-issue-tag branch 2 times, most recently from 0ef281a to 2f3514b Compare February 13, 2025 19:54
@murilx murilx marked this pull request as ready for review February 13, 2025 20:14
@murilx murilx force-pushed the feat/new-issue-tag branch from 2f3514b to eb5ebd5 Compare February 14, 2025 11:13
@murilx murilx force-pushed the feat/new-issue-tag branch from eb5ebd5 to 6ce925d Compare February 14, 2025 11:38
Copy link
Collaborator

@MarceloRobert MarceloRobert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to be working well, nice job

@@ -196,6 +197,7 @@ export const messages = {
'hardwareDetails.treeBranch': 'Tree / Branch',
'issue.alsoPresentTooltip': 'Issue also present in {tree}',
'issue.firstSeen': 'First seen',
'issue.newIssue': 'This issue is new to this tree',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The meaning of the "new" tag is not just "to this tree",

Suggested change
'issue.newIssue': 'This issue is new to this tree',
'issue.newIssue': 'This is the first time this issue was seen',

You can think of a tooltip that's better than my suggestion, but something along those lines

Copy link
Collaborator

@WilsonNet WilsonNet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice job

- Changed the issuesExtra response to include more info about the first
  incident of each issue, including commit hash, git branch and git url
- Added the pill to the issue list if the commit hash of the first
  incident is the same commit hash of the tree details page

Closes #571
@murilx murilx force-pushed the feat/new-issue-tag branch from 6ce925d to fb07e54 Compare February 14, 2025 18:26
@murilx murilx merged commit 75e9880 into main Feb 14, 2025
5 checks passed
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

Successfully merging this pull request may close these issues.

Add NEW to issues that appeared on current revision
3 participants