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

feat(ci): Add GitHub Action to validate dependabot config #100

Open
mark-stopka opened this issue Jan 25, 2022 · 4 comments
Open

feat(ci): Add GitHub Action to validate dependabot config #100

mark-stopka opened this issue Jan 25, 2022 · 4 comments
Assignees
@mark-stopka
Labels
automation enhancement New feature or request
Milestone
v2.0.0

Comments

@mark-stopka
Copy link
Collaborator

@mark-stopka mark-stopka added enhancement New feature or request automation labels Jan 25, 2022
@mark-stopka mark-stopka added this to the v1.3 milestone Jan 25, 2022
@mark-stopka mark-stopka self-assigned this Jan 25, 2022
@mark-stopka mark-stopka moved this to Refinement in Oura Development Jan 25, 2022
@mark-stopka mark-stopka mentioned this issue Jan 25, 2022
Merged
@mark-stopka
Copy link
Collaborator Author

Following GitHub action has an issue marocchino/validate-dependabot#233

@mark-stopka mark-stopka moved this from Refinement to Todo in Oura Development Jan 27, 2022
@mark-stopka mark-stopka modified the milestones: v1.3, v2.0.0 Jan 27, 2022
@mark-stopka
Copy link
Collaborator Author

Issue is related to upstream dependabot/dependabot-core#4605

@mark-stopka mark-stopka changed the title Add GitHub Action to validate dependabot config feat(ci): Add GitHub Action to validate dependabot config Jan 28, 2022
@scarmuega
Copy link
Member

the dependabot config is rarely updated, adding a whole new CI workflow for validating changes on that single file seems excessive.

Am I missing something? Do you foresee frequent changes in the dependabot config? If we do need some kind of validation, couldn't it be ran as part of existing linting step?

@mark-stopka
Copy link
Collaborator Author

It would indeed be part of an existing linting, however the GH Action that does that is currently broken, so I am just waiting for upstream to fix it, should not take long, the dev said "few weeks". So it would be just one more step after .editorconfig validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mark-stopka mark-stopka

Labels
automation enhancement New feature or request
Projects
Development
Status: No status
Oura Development
Archived in project
Milestone
v2.0.0
Development

No branches or pull requests
2 participants
@scarmuega @mark-stopka