Fix the logic to generate .pro file - #664
Merged
DellaBitta merged 4 commits intoSep 15, 2021
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
a-maurice
approved these changes
Sep 15, 2021
DellaBitta
requested changes
Sep 15, 2021
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Release notes should be under 8.5.0.
You should merge main into your branch first to see the 8.5.0 release notes header in your branch.
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
Updated |
Sorry, something went wrong.
added 2 commits
September 15, 2021 10:49
DellaBitta
approved these changes
Sep 15, 2021
Copy link
Copy Markdown
❌ Integration test FAILEDRequested by @DellaBitta on commit 2008044
Add flaky tests to go/fpl-cpp-flake-tracker |
Sorry, something went wrong.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reviewers
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To address issue #604