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

system tests: prevent leading tabs #17518

Merged
merged 1 commit into from
Feb 16, 2023

Conversation

edsantiago
Copy link
Member

Replace existing tab indentations with spaces, and add
a test to CI to prevent new ones from sneaking in.

Signed-off-by: Ed Santiago [email protected]

None

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 15, 2023
Replace existing tab indentations with spaces, and add
a test to CI to prevent new ones from sneaking in.

Signed-off-by: Ed Santiago <[email protected]>
@edsantiago
Copy link
Member Author

Checking for leading tabs in system tests
test/system/800-config.bats:65:	is "$output" "Error:.*no such container" "unexpected error from podman wait"
************************************************
ERROR: Found leading tabs in system tests. Use spaces to indent, not tabs.  (contrib/cirrus/prebuild.sh:33 in main())
************************************************

This was intentional, as confirmation that the new no-more-tabs check works. It does. Repushed with clean tab-less code.

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

Yes, please
LGTM!

@Luap99
Copy link
Member

Luap99 commented Feb 15, 2023

If we do not want to blow up CI on main, we should properly check other PRs for tabs before we merge this.

@edsantiago
Copy link
Member Author

Well, #17386 is the obvious one. If that one merges first, I will rebase mine. But I do hope Dan fixes the whitespace issues before that merges.

I have no automated way to check in-flight PRs, so if worst comes to worst, it'll have to be fixed in the affected PRs.

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

/lgtm

Farewell my beloved tabs...

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2023
@openshift-merge-robot openshift-merge-robot merged commit e8a8433 into containers:main Feb 16, 2023
@edsantiago edsantiago deleted the untab branch February 16, 2023 11:11
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 9, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants