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

Configure Dependabot using a YAML config file #1650

Closed
1 task
zackkrida opened this issue Feb 21, 2022 · 3 comments · Fixed by WordPress/openverse-catalog#740
Closed
1 task

Configure Dependabot using a YAML config file #1650

zackkrida opened this issue Feb 21, 2022 · 3 comments · Fixed by WordPress/openverse-catalog#740
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed

Comments

@zackkrida
Copy link
Member

Description

For this repository, Dependabot is enabled but not configured. Adding a .github/dependabot.yml file should fix that. Using the file we can configure things like the update schedule and the labels to attach to the PRs made by Dependabot.

Expectation

Dependabot should make regular, well-labeled PRs to the repository.

Additional context

You can use the config from the API repo as a reference. Also see the GitHub docs describing this config file.

Resolution

  • 🙋 I would be interested in resolving this bug.
@zackkrida zackkrida added 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository labels Feb 21, 2022
@zackkrida zackkrida added good first issue New-contributor friendly help wanted Open to participation from the community and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Feb 21, 2022
@AetherUnbound
Copy link
Collaborator

Part of the reason we don't have dependabot set up on this repo is that Airflow is very particular about its dependencies. So much so that the installation instructions from PyPI specifically describe using the provided constraints file for a given version. This constraints file dictates all of the dependencies that Airflow interacts with; it does not pin dependencies for everything available in PyPI. I think we can look into using dependabot here, but we might need to restrict it to only the dev dependencies (or even just a subset of our dependencies) as it's likely that the versions dependabot suggests will conflict with the provided constraints file.

@zackkrida zackkrida added 🟩 priority: low Low priority and doesn't need to be rushed and removed 🟧 priority: high Stalls work on the project or its dependents labels Mar 29, 2022
@obulat obulat removed their assignment Jun 18, 2022
@obulat
Copy link
Contributor

obulat commented Jun 18, 2022

Unassigning myself from this issue because I'm not sure how to proceed. We are using Renovate for the other repositories now. Should we close this issue altogether?

@AetherUnbound
Copy link
Collaborator

We could certainly use Renovate for the dev dependencies, if that's something it's capable of doing!

@obulat obulat transferred this issue from WordPress/openverse-catalog Apr 17, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Apr 17, 2023
@obulat obulat moved this from 📋 Backlog to ✅ Done in Openverse Backlog Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix good first issue New-contributor friendly help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants