[ACA-100] View a previous version #5880
Closed
Conversation
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
ursedaniel
requested review from
cristinaj,
DenysVuika,
eromano,
m-hulbert and
popovicsandras
as code owners
eromano
force-pushed
the
dev-durse-ACA-100-ng10
branch
from
f8693c7
to
25b50cf
Compare
|
/rebase |
|
I see "develop" is now green again :-) What's left to do to get this one over the merge line (ie. fixing this branch build) ... cc @ursedaniel @eromano @KikoUK |
|
/rebase |
|
It looks like the last merge from "develop" to this branch was 4 days ago. Can we update again ( cc @ursedaniel @KikoUK ) and fix the compilation issues in previous PR build ? |
|
Created a fresh one because of the failing travis. #5913 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: