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

SONARPY-2429: Merge the ruling and the extended ruling #2232

Merged
merged 7 commits into from
Dec 11, 2024

Conversation

Seppli11
Copy link
Contributor

@Seppli11 Seppli11 commented Dec 10, 2024

SONARPY-2429

This PR is based on SONARPY-2430. Therefore, SONARPY-2430 has to be merged before this PR can be merged into ruling-parallelization-master

@Seppli11 Seppli11 changed the base branch from master to ruling-parallelization-master December 10, 2024 13:21
@Seppli11 Seppli11 changed the base branch from ruling-parallelization-master to SONARPY-2130 December 10, 2024 13:21
@Seppli11 Seppli11 changed the base branch from SONARPY-2130 to SONARPY-2430 December 10, 2024 13:22
@Seppli11 Seppli11 force-pushed the SONARPY-2429 branch 4 times, most recently from ee59e91 to ffb353e Compare December 10, 2024 15:11
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks good! I just have one question, because I don't understand how the current submodule setup works, but this looks very promising!

.gitmodules Outdated
[submodule "its/sources_extended"]
path = its/sources_extended
[submodule "its/sources_ruling"]
path = its/sources_ruling
url = https://github.com/SonarCommunity/python-test-sources.git
branch = extended

Choose a reason for hiding this comment

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

I'm a bit confused here, how are we actually retaining the original ruling sources (from master)? It seems the only submodule defined is for the extended branch and that branch hasn't changed?
I'd have expected to see the master-temp branch here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

On the python-test-sources side, I've essentially merged the two branches into master-temp, which is checked out in the its/sources_ruling submodule.
According to this StackOverflow answer, git keeps track of the hash of the submodules directly in its database. That's probably the reason for the following diff
image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've changed the .gitmodules and added shallow = true (see here for documentation)

@Seppli11 Seppli11 force-pushed the SONARPY-2429 branch 2 times, most recently from 2b17964 to 987e442 Compare December 11, 2024 14:43
Base automatically changed from SONARPY-2430 to ruling-parallelization-master December 11, 2024 15:02
Copy link

sonarqube-next bot commented Dec 11, 2024

Quality Gate passed Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

Copy link
Contributor

@guillaume-dequenne-sonarsource guillaume-dequenne-sonarsource left a comment

Choose a reason for hiding this comment

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

LGTM!
Please address the issue on Next before merging (I think we can simply accept it tbh).

@Seppli11 Seppli11 merged commit 818da5a into ruling-parallelization-master Dec 11, 2024
12 checks passed
@Seppli11 Seppli11 deleted the SONARPY-2429 branch December 11, 2024 16:06
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.

2 participants