check: Fix handling of <remove-project /> element #37
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.
When
repo-resource
creates a version string (which is a full XML representation of a manifest), the<remove-project>
tag is not taken into account.Because of this, we generate "false positives" for new Versions, which could trigger unwanted builds.
For example, with manifest [1], we see that the Version string has the device/amlogic/yukawa project twice, which is wrong.
Handle the element to fix this.
[1] https://github.com/makohoek/demo-manifests/blob/main/aosp_remove_yukawa_project.xml
Fixes: #36
Fixes: c23fc0c ("Switch to getRevision code based on git ls-remote")
Signed-off-by: Mattijs Korpershoek mkorpershoek@baylibre.com