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

If no experiments are specified, use the GitHub defaults #1514

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rhyskoedijk
Copy link
Contributor

@rhyskoedijk rhyskoedijk commented Dec 14, 2024

More closely match the behavior of the GitHub hosted Dependabot service by using the same default experiments. If the user explicitly sets the experiments task input, the default will not be used.

This PR also cleans up some of the documentation, fixes several inaccuracies and removes things which don't add much value anymore (e.g. V1 auth workarounds).

@@ -104,41 +135,6 @@ BUT the values will be used from pipeline environment variables. Template variab
> 1. Have `Packaging (Read)` permission.
> 2. Be issued by a user with permission to the feed either directly or via a group. An easy way for this is to give `Contributor` permissions the `[{project_name}]\Contributors` group under the `Feed Settings -> Permissions` page. The page has the url format: `https://dev.azure.com/{organization}/{project}/_packaging?_a=settings&feed={feed-name}&view=permissions`.

> [!NOTE]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought it would be good to drop this from to reduce confusion and complexity given using V1 is discouraged now, any concerns?


- [Azure DevOps Extension](https://marketplace.visualstudio.com/items?itemName=tingle-software.dependabot) - Ideal if you want to get Dependabot running with minimal administrative effort. The extension can run directly inside your existing pipeline agents and doesn't require hosting of any additional services. Because the extension runs in pipelines, this option does **not** scale well if you have a large number of projects and repositories.

<details>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I read an issue or two recently that suggested maybe people weren't finding the "getting started" pipeline example from /extension/README.MD, so though it might be worthwhile pasting it at the top of the root read me too for visibility. Thoughts?

@rhyskoedijk rhyskoedijk marked this pull request as ready for review December 16, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant