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: display PR Cycle Time info #179

Conversation

power-f-GOD
Copy link
Contributor

@power-f-GOD power-f-GOD commented Oct 19, 2023

Resolves: #166

Screenshot 2023-10-19 at 2 58 42 PM

TA: 3hrs (-> 4hrs)

@vercel
Copy link

vercel bot commented Oct 19, 2023

@power-f-GOD is attempting to deploy a commit to the Holdex Accelerator Team on Vercel.

To accomplish this, @power-f-GOD needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

@@ -65,7 +65,7 @@ module.exports = {
],
'no-floating-decimal': 'warn',
'no-implicit-coercion': [
'error',
'off',
Copy link
Member

Choose a reason for hiding this comment

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

why?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

why?

Ok. I got tired of the linter converting my succinct !!<expression>s to Boolean(<expression>), and also TypeScript not being able to infer the truthiness of Boolean when used in a ternary check or similar.

E.g.

// errs
let a: Record<string, any> | null  = { b: 1 };
let c = Boolean(a) ? a.b : 1; // TS-check (linter) error: `a` is possibly `null`

// doesn't err
let a: Record<string, any> | null  = { b: 1 };
let c = !!a ? a.b : 1; // No errors

@zolotokrylin
Copy link
Member

@power-f-GOD is this ready for review or is it WIP?
If WIP, the 3 hours have passed already a long time ago. Why is this PR still hanging?

@power-f-GOD power-f-GOD changed the title feat: see PR "Cycle Time". [draft] feat: see PR "Cycle Time". Oct 24, 2023
@power-f-GOD
Copy link
Contributor Author

@power-f-GOD is this ready for review or is it WIP?

Yes, it is, but previous PRs have to be reviewed and merged first. This first: #175.

Cc: @georgeciubotaru

…st-in-usd--add-rate' into 127-problem-as-sponsor-i-cant-see-the-actual-feature-cost-in-usd--cost-breakdown
@zolotokrylin
Copy link
Member

@power-f-GOD the previous PR was merged. What's next?

@power-f-GOD
Copy link
Contributor Author

power-f-GOD commented Oct 30, 2023

@power-f-GOD the previous PR was merged. What's next?

Notice I said "PRs" not "PR".

This is next: #176

Cc: @georgeciubotaru

Base automatically changed from 177-problem-manager-cant-see-pr-participants-at-first-glance to main October 30, 2023 13:07
@power-f-GOD power-f-GOD changed the title [draft] feat: see PR "Cycle Time". feat: see PR "Cycle Time". Oct 30, 2023
@power-f-GOD power-f-GOD changed the title feat: see PR "Cycle Time". feat: see PR "Cycle Time" Oct 30, 2023
…st-in-usd--cost-breakdown' into 166-problem-i-cant-see-all-open-prs-per-by-developer-and-how-many-hours-ago-was-open--cycle-time
…lance' into 166-problem-i-cant-see-all-open-prs-per-by-developer-and-how-many-hours-ago-was-open--cycle-time
@power-f-GOD
Copy link
Contributor Author

@georgeciubotaru , Please, merge #183 first before the current PR.

@georgeciubotaru
Copy link
Contributor

@power-f-GOD Please resolve the conflicts

@zolotokrylin
Copy link
Member

Did you forget to use REQUEST REVIEW feature?

@power-f-GOD
Copy link
Contributor Author

Did you forget to use REQUEST REVIEW feature?

I forgot this one time.😅 But that was because George got here before me after he merged the preceeding PR.

@power-f-GOD
Copy link
Contributor Author

@georgeciubotaru 🤲🏼

@georgeciubotaru georgeciubotaru changed the title feat: see PR "Cycle Time" feat: display PR Cycle Time info Oct 31, 2023
@georgeciubotaru georgeciubotaru merged commit edb7427 into main Oct 31, 2023
@georgeciubotaru georgeciubotaru deleted the 166-problem-i-cant-see-all-open-prs-per-by-developer-and-how-many-hours-ago-was-open--cycle-time branch October 31, 2023 09:29
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.

Problem: I can't see all open PRs per by developer (and how many hours ago was open)
3 participants