Skip to content

CI/CD now covers ./features, made func less strict, adjusted/fixed tests - #219

Merged
pjljvandelaar merged 10 commits into
mainfrom
ci-include-features
Sep 30, 2026
Merged

pjljvandelaar merged 10 commits into
mainfrom
ci-include-features

Conversation

@FrancescoPezzella

@FrancescoPezzella FrancescoPezzella commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes #218

@FrancescoPezzella FrancescoPezzella self-assigned this Sep 24, 2026
@FrancescoPezzella

Copy link
Copy Markdown
Collaborator Author

The tests started failing when the proper detection was added by #177

@FrancescoPezzella

Copy link
Copy Markdown
Collaborator Author

@pjljvandelaar Can I get more specification from you whether my change is in the right direction or not? 0d33c25

In this commit, when I made the duplicate rewriter detection system, it turned out to be too strict. I could have made the tests failing, but is no reason, since duplicates rewrites (something I believe Corvino mention during your brief discussion) are not always an issue. So the function is less strict now.

@FrancescoPezzella
FrancescoPezzella marked this pull request as ready for review September 25, 2026 13:03
@FrancescoPezzella FrancescoPezzella changed the title CI/CD now covers ./features CI/CD now covers ./features, made func less strict, adjusted/fixed tests Sep 25, 2026
@FrancescoPezzella FrancescoPezzella added the enhancement New feature or request label Sep 25, 2026
Automatic Python lint fixes

Pipeline should now properly fail
…OVE/REPLACE condition needs this check. For other conditions, it does not need to be so strict.

This causes most of the tests to work again, since they do not have to follow such strict requirements.
Comment thread .github/workflows/docs-quality.yml
Comment thread .github/workflows/python-package.yml

@pjljvandelaar pjljvandelaar left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Do you agree that we should accept it now, and later on change it again once the new structure is made effective?

@FrancescoPezzella

Copy link
Copy Markdown
Collaborator Author

Do you agree that we should accept it now, and later on change it again once the new structure is made effective?

I believe it should be accepted now. The architectural change is a separate issue, and the only thing that will change is that Ci/Cd no longer needs to cover ./features. All the other changes would stay more or less the same, so I don't really see a reason for it not be accepted separately.

@pjljvandelaar
pjljvandelaar merged commit 0bf2161 into main Sep 30, 2026
10 checks passed
@pjljvandelaar
pjljvandelaar deleted the ci-include-features branch September 30, 2026 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tests fail on main

2 participants