devcontainers / devcontainers/cli

Add smoke test against Dependabot integration

Ouverte
#732 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
feature-request
Langage dominant
TypeScript
Étoiles
3k
Forks
457
Merge moyen
13 h 17 min
PR mergées (30 j)
6

Description

Now that the CLI is coupled to the [dependabot integration ](https://containers.dev/guide/dependabot), it would be great to have an automated PR check to confirm changes are compatible. The `devcontainer outdated`, `devcontainer features info`, and `devcontainer upgrade` commands are all utilized in the [dependabot core implementation](https://github.com/dependabot/dependabot-core/pull/8445)

This should be fairly straightforward to create a test for, given that the project is highly containerized. The [dev container ecosystem container](https://github.com/dependabot/dependabot-core/pkgs/container/dependabot-updater-devcontainers) can be rebuilt using the dev build of the CLI:

The dependabot CLI can then be utilized to run a sanity check:

```
LOCAL_GITHUB_ACCESS_TOKEN="$LOCAL_GITHUB_ACCESS_TOKEN" dependabot \
--updater-image ghcr.io/dependabot/dependabot-updater-devcontainers \
update \
devcontainers \
joshspicer/versioning-project-two-configs \
-o /tmp/updates.yaml \
--directory /

updater | +-----------------------------------------------------------------------+
updater | | Changes to Dependabot Pull Requests |
updater | +---------+-------------------------------------------------------------+
updater | | created | ghcr.io/codspace/versioning/foo:1 ( from 1.1.0 to 2.11.1 ) |
updater | | created | ghcr.io/codspace/versioning/baz:1.0 ( from 1.0.0 to 2.0.0 ) |
updater | +---------+-------------------------------------------------------------+
```

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.