Skip to content

[$1000] test #75

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.

Sign up for GitHub

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

Jump to bottom
Open
puneetlath opened this issue Oct 25, 2022 · 65 comments
Open

[$1000] test #75

puneetlath opened this issue Oct 25, 2022 · 65 comments
Assignees
@chiragsalian @trjExpensify @parasharrajat
Labels
Bug Something isn't working Concierge Daily Engineering Internal

Comments

@puneetlath
Copy link
Owner

puneetlath commented Oct 25, 2022 •
edited
Loading

test

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021613956225432604672
  • Upwork Job ID: 1613956225432604672
  • Last Price Increase: 2023-01-13
@puneetlath
Copy link
Owner Author

Triggered auto assignment to @joekaufmanexpensify (Concierge), see https://stackoverflow.com/c/expensify/posts/tagged/950 for more details.

@puneetlath
Copy link
Owner Author

Test issue, you can ignore.

@puneetlath puneetlath added the Bug Something isn't working label Oct 31, 2022
@puneetlath
Copy link
Owner Author

Triggered auto assignment to @arielgreen (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@puneetlath puneetlath mentioned this issue Oct 31, 2022
Merged
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the updated test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

1 similar comment
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the updated test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

This was referenced Oct 31, 2022
Merged
Merged
Merged
Merged
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the updated test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

This was referenced Nov 4, 2022
Merged
Merged
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

1 similar comment
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

This was referenced Nov 4, 2022
Merged
Merged
Merged
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

1 similar comment
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

@puneetlath puneetlath mentioned this issue Nov 4, 2022
Merged
@puneetlath puneetlath self-assigned this Nov 4, 2022
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

1 similar comment
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

@puneetlath puneetlath mentioned this issue Nov 4, 2022
Merged
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

1 similar comment
@puneetlath
Copy link
Owner Author

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  • The PR that introduced the bug has been identified. Link to the PR:
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • A discussion in #contributor-plus has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • Payment has been made to the issue reporter (if applicable)
  • Payment has been made to the contributor that fixed the issue (if applicable)
  • Payment has been made to the contributor+ that helped on the issue (if applicable)

@puneetlath
Copy link
Owner Author

@chiragsalian @trjExpensify @parasharrajat this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

@puneetlath
Copy link
Owner Author

Current assignee @trjExpensify is eligible for the External assigner, not assigning anyone new.

@puneetlath puneetlath added Daily and removed Weekly labels Jan 13, 2023
@puneetlath
Copy link
Owner Author

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

@puneetlath
Copy link
Owner Author

Current assignee @chiragsalian is eligible for the External assigner, not assigning anyone new.

@puneetlath
Copy link
Owner Author

@chiragsalian @trjExpensify @parasharrajat this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

@puneetlath
Copy link
Owner Author

@chiragsalian @trjExpensify @parasharrajat this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

@puneetlath
Copy link
Owner Author

Current assignee @trjExpensify is eligible for the External assigner, not assigning anyone new.

@puneetlath
Copy link
Owner Author

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

@puneetlath
Copy link
Owner Author

Current assignee @chiragsalian is eligible for the External assigner, not assigning anyone new.

@puneetlath
Copy link
Owner Author

@chiragsalian @trjExpensify @parasharrajat this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:

  • Decide whether any proposals currently meet our guidelines and can be approved as-is today
  • If no proposals meet that standard, please take this issue internal and treat it as one of your highest priorities
  • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

Thanks!

@puneetlath puneetlath added Monthly and removed External Help Wanted Extra attention is needed Daily labels Jan 13, 2023
@puneetlath
Copy link
Owner Author

@chiragsalian @trjExpensify @parasharrajat this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

@puneetlath puneetlath added Daily and removed Monthly labels Jan 13, 2023
@puneetlath
Copy link
Owner Author

Sorry for the spam everyone! Just testing the new WAQ issue bumping.

@chiragsalian
Copy link
Collaborator

Its all cool 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chiragsalian chiragsalian

@trjExpensify trjExpensify

@parasharrajat parasharrajat

Labels
Bug Something isn't working Concierge Daily Engineering Internal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@puneetlath @chiragsalian @trjExpensify @parasharrajat