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

Support changelogs from Azure DevOps #18324

Open
sch1ldkr0ete opened this issue Oct 13, 2022 · 11 comments
Open

Support changelogs from Azure DevOps #18324

sch1ldkr0ete opened this issue Oct 13, 2022 · 11 comments
Labels
core:changelogs Related to changelogs/release notes fetching help wanted Help is needed or welcomed on this issue platform:azure Azure DevOps platform priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@sch1ldkr0ete
Copy link
Contributor

What would you like Renovate to be able to do?

Fetch changelogs from Azure DevOps and add the changelog to the PR.

If you have any ideas on how this should be implemented, please tell us here.

Changelog fetching is already implemented for GitHub and GitLab. So we could implement something analog for Azure DevOps using the Azure DevOps Services REST API.

Implementing this could be blocked by #14138 though.

Is this a feature you are interested in implementing yourself?

Yes

@sch1ldkr0ete sch1ldkr0ete added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels Oct 13, 2022
@HonkingGoose HonkingGoose added core:changelogs Related to changelogs/release notes fetching platform:azure Azure DevOps platform labels Oct 13, 2022
@HonkingGoose
Copy link
Collaborator

@viceice Can you take a look at this issue? Maybe you want to add it to your big to-do list in #14138?

@rarkins rarkins added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:ready and removed status:requirements Full requirements are not yet known, so implementation should not be started priority-5-triage labels Oct 14, 2022
@rarkins
Copy link
Collaborator

rarkins commented Oct 14, 2022

We have not made any progress on a big rewrite and I wouldn't want to stand in the way of someone adding a useful feature for themselves and others. If it can be done with more if/else statements.. so be it.

@sorensenmatias

This comment has been minimized.

illay1994 added a commit to illay1994/renovate that referenced this issue Oct 25, 2023
@illay1994

This comment has been minimized.

@rarkins

This comment has been minimized.

@illay1994

This comment has been minimized.

@rarkins

This comment has been minimized.

@illay1994

This comment has been minimized.

@ceng-p

This comment has been minimized.

@illay1994

This comment has been minimized.

@rarkins rarkins added the help wanted Help is needed or welcomed on this issue label Apr 16, 2024
@sheldonhull

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core:changelogs Related to changelogs/release notes fetching help wanted Help is needed or welcomed on this issue platform:azure Azure DevOps platform priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants