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

[No QA] Use deploy blocker title instead of bad markdown in Slack comment #2991

Merged
merged 2 commits into from
May 18, 2021

Conversation

roryabraham
Copy link
Contributor

@roryabraham roryabraham commented May 18, 2021

@rafecolton Will you please review this?

Details

When a new E.cash deploy blocker is created, post the issue title in the #deployer slack room.

Fixed Issues

n/a – slack convo here

Testing plan

  1. Merge this PR.
  2. Create a new E.cash issue labelled DeployBlockerCash
  3. Verify that the slack post in #deployer includes the issue title as a hyperlink back to the issue you created in the previous step.

@roryabraham roryabraham requested a review from rafecolton May 18, 2021 21:07
@roryabraham roryabraham self-assigned this May 18, 2021
@roryabraham roryabraham requested a review from a team as a code owner May 18, 2021 21:07
@MelvinBot MelvinBot requested review from jasperhuangg and removed request for a team May 18, 2021 21:08
@roryabraham roryabraham requested a review from rafecolton May 18, 2021 21:35
Copy link
Member

@rafecolton rafecolton left a comment

Choose a reason for hiding this comment

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

LGTM

@rafecolton rafecolton merged commit f1c770f into main May 18, 2021
@rafecolton rafecolton deleted the Rory-DeployBlockerCommentIssueTitle branch May 18, 2021 22:45
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@AndrewGable
Copy link
Contributor

Why not ping #expensify-open-source (or both)?

@roryabraham
Copy link
Contributor Author

We could potentially do that ... part of the discussion here was that deploy-blockers should be internal, so that we know they'll be treated with a high degree of urgency. Even if a contributor can quickly see a solution to the deploy blocker, we often won't want to triage, create and upwork job, wait for their proposal, etc... Thoughts?

@AndrewGable
Copy link
Contributor

Seems OK for now 👍

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.

4 participants