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.

Sign up for GitHub

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

Jump to bottom

For some options, verify all versions of the repository #15

Open
craigez opened this issue Jun 13, 2017 · 6 comments · May be fixed by #293
Open

For some options, verify all versions of the repository #15

craigez opened this issue Jun 13, 2017 · 6 comments · May be fixed by #293
Labels
enhancement

Comments

@craigez
Copy link
Contributor

craigez commented Jun 13, 2017

For example, it might be useful to verify certain file types are not present in ANY branch/version of the repository. Similar with file contents, etc...

I expect this would be optional behavior as it could be very expensive for some repositories.
@craigez craigez changed the title For some file related options, verify all versions of the repository For some options, verify all versions of the repository Jun 13, 2017
@craigez
Copy link
Contributor Author

craigez commented Jun 13, 2017

Password checking would also be a check that may want to run in this manner

@iamwillbar
Copy link
Contributor

Are you thinking on every commit or just every tag/branch? Password checking would need every commit but I'd imagine you wouldn't want this for most rules.

@craigez
Copy link
Contributor Author

craigez commented Jun 14, 2017

For the immediate use case I had in mind (binaries) I would ideally want every commit, though at every tag/branch probably finds 99% of the issues.

@hyandell
Copy link
Member

I'd be tempted for this to be a separate project. System to run on every commit/branch/release/whatever.

@craigez
Copy link
Contributor Author

craigez commented Feb 27, 2018

I've been looking at this in some other contexts using ref-log to easily search all the changes without duplication. I'll bring back whatever we end up doing there for discussion in this forum.

@Brend-Smits Brend-Smits linked a pull request Mar 31, 2023 that will close this issue
Open
@Brend-Smits
Copy link
Collaborator

Better late than never! I opened a PR to hopefully resolve this issue. We have been using this feature for some time now to check for content in a certain file (CNAME), in both the default and the gh-pages branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add ability to specify branches for (any)-file-content rules philips-forks/repolinter
4 participants
@hyandell @iamwillbar @craigez @Brend-Smits