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

Implement more flexible regex parsing of StagingDeployCash issues #2776

Merged
merged 1 commit into from
May 11, 2021

Conversation

roryabraham
Copy link
Contributor

Details

As discussed 1:1, this small improvement to the regex parsing of StagingDeployCash issues should make them more flexible and allow me to easily edit it to add missing pull requests without breaking the parsing.

Fixed Issues

n/a

Tests

Added a unit test that duplicates a success case, except w/o any carriage returns.

QA Steps

No QA.

Tested On

Unit tested only. Will be live tested on GitHub.

@roryabraham roryabraham requested a review from AndrewGable May 10, 2021 23:41
@roryabraham roryabraham self-assigned this May 10, 2021
@roryabraham roryabraham requested a review from a team as a code owner May 10, 2021 23:41
@MelvinBot MelvinBot requested review from Luke9389 and removed request for a team May 10, 2021 23:41
@roryabraham roryabraham merged commit 824f988 into main May 11, 2021
@roryabraham roryabraham deleted the Rory-MoreFlexibleParsingRegexes branch May 11, 2021 16:27
@roryabraham
Copy link
Contributor Author

Self-merging this so I can add PRs that are missing from the checklist!

@OSBotify
Copy link
Contributor

🚀 Deployed to staging in version: 1.0.41-11🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production in version: 1.0.44-0🚀

platform result
🤖 android 🤖 failure ❌
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

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.

3 participants