-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into vit-updateArchiveMessageForAdmin
- Loading branch information
Showing
117 changed files
with
19,268 additions
and
2,524 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
name: Design Doc tracking issue | ||
about: A standard template to follow when leading a project | ||
labels: Daily, NewFeature | ||
--- | ||
|
||
## Proposal | ||
|
||
## Tasks | ||
|
||
- [ ] Post **Proposal (full Problem/Solution statement)** in `#expensify-open-source` | ||
- [ ] Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍) | ||
- [ ] Paste Proposal in the space above with a link to the Slack thread | ||
- [ ] Email `strategy@expensify.com` and paste in the Proposal | ||
- [ ] Fill out the **High-level overview of the problem**, **Timeline**, and **Terminology** sections of the Design Doc | ||
- [ ] Email `strategy@expensify.com` (continue the same email chain as before) with the link to your Design Doc | ||
- [ ] Host a **pre-design** meeting ([example](https://expensify.slack.com/archives/C01GTK53T8Q/p1665794669539419)) in `#expensify-open-source` to discuss any necessary details in public before filling out the **High-level of proposed solution** section. | ||
- [ ] Fill out the **High-level of proposed solution** section | ||
- [ ] Email `stategy@expensify.com` again with links to the doc and pre-design conversation in Slack | ||
- [ ] Add the `DesignDocReview` label to get the **High-level of proposed solution** section reviewed | ||
- [ ] Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary | ||
- [ ] Confirm that the doc has the minimum necessary number of reviews before proceeding | ||
- [ ] Host another pre-design meeting in `#expensify-open-source` to ask for engineering feedback on the technical solution. | ||
- [ ] Fill out the **Detailed implementation of the solution** and related sections. | ||
- [ ] Re-add the `DesignDocReview` label to this issue | ||
- [ ] Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary | ||
- [ ] Confirm that the doc has the minimum necessary number of reviews before proceeding | ||
- [ ] Email `strategy@expensify.com` one last time to let them know the Design Doc is moving into the implementation phase | ||
- [ ] Implement the changes | ||
- [ ] Send out a follow up email to `strategy@expensify.com` once everything has been implemented and do a **Project Wrap-Up** retrospective that provides: | ||
- Summary of what we accomplished with this project | ||
- What went well? | ||
- What could we have done better? | ||
- What did we learn? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
36 changes: 36 additions & 0 deletions
36
.github/actions/javascript/postTestBuildComment/action.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
name: "Mark Pull Requests as Deployed" | ||
description: "Mark pull requests as deployed on production or staging" | ||
inputs: | ||
PR_NUMBER: | ||
description: "Pull request number" | ||
required: true | ||
GITHUB_TOKEN: | ||
description: "Github token for authentication" | ||
default: "${{ github.token }}" | ||
ANDROID: | ||
description: "Android job result ('success', 'failure', 'cancelled', or 'skipped')" | ||
required: true | ||
DESKTOP: | ||
description: "Desktop job result ('success', 'failure', 'cancelled', or 'skipped')" | ||
required: true | ||
IOS: | ||
description: "iOS job result ('success', 'failure', 'cancelled', or 'skipped')" | ||
required: true | ||
WEB: | ||
description: "Web job result ('success', 'failure', 'cancelled', or 'skipped')" | ||
required: true | ||
ANDROID_LINK: | ||
description: "Link for the Android build" | ||
required: false | ||
DESKTOP_LINK: | ||
description: "Link for the desktop build" | ||
required: false | ||
IOS_LINK: | ||
description: "Link for the iOS build" | ||
required: false | ||
WEB_LINK: | ||
description: "Link for the web build" | ||
required: false | ||
runs: | ||
using: "node16" | ||
main: "./index.js" |
Oops, something went wrong.