Capabilities of Dependabot in GitHub with Azure Artifacts - Blogs
X
12Aug

Capabilities of Dependabot in GitHub with Azure Artifacts

In GitHub, while you can see a list of packages the organization level, the packages are installed to a specific repository. We can see here the instructions for pushing various package ecosystems to GitHub npm, NuGet, Maven, Docker. In case you are storing artifacts/packages in Azure Artifacts, Dependabot also supports private feeds, including Azure Artifacts. We can easily configure that in GitHub simply by providing required credentials from Azure Artifacts.

Configuration Dependabot in GitHub:

Firstly, we have to setup Dependabot secret, in the organization level or repository level under the dependabot section as show below & here

 

dependabot-secret

 

Add the below configuration in the .github/dependabot.yml

dependabot

 

Shortly after committing the dependabot.yml file, we can confirm it works as there’s a new Pull Request from Dependabot with package residing in Azure Artifacts

PR-dependabot

 

We can also look at our Dependabot logs:

dependabot-logs

 

Even though you might have the schedule set to “daily”, Dependabot will run again if you push a change to the .github/dependabot.yml. You can also run it manually at any time by navigating to:

Insights    Dependency Graph     Dependabot     Check for updates

 

Pull request limit

  • By default, the limit is 5, so Dependabot will only create 5 pull requests for version updates.
  • If you check your pull requests, you might see you have more than 5, but some of those might be Dependabot Security Alerts, which don’t count to that limit.
  • You can also increase the limit by adding the below line in the config file.

                                      “open-pull-requests-limit: 15”

Conclusion:

  • Maintaining your internally created packages up to date is made a lot easier by being able to use Dependabot with Azure Artifacts.
  • Automatically be informed when a new version of the package is available, and following a successful build and passing unit tests, you can accept and merge the Pull-Request.
  • If a team doesn’t want to use the updated version, they can simply close the Pull-Request and it won’t be re-opened until a new version of the package is released.

Related

How to use Model Binding with ASP.NET Data Controls

IntroductionASP.NET 4.5 provides a flexible alternative to server data controls called as, Model Bin...

Read More >

NODE AFFINITY

The k8s node affinity feature is to ensure pods are hosted on a particular node. As mentioned in pre...

Read More >

CxO Roundtable at C-SOaP- SUMMIT 2013

   img{ display:block; } #outlook a{ padding:0; } body{ width:100% !importa...

Read More >

What's New in Microsoft Dynamics NAV 2017

We were hearing about Dynamics NAV 2017 since long time that it will be releasing by the end of 2016...

Read More >

Dynamics Team commences work on NAV Version Migration for a prestigious client in Malaysia

Canarys Dynamics Team is all excited and geared up to commence work on NAV Version Migration project...

Read More >

Threading

Multi-taskingIt is a concept of performing multiple tasks over a certain period of time by executing...

Read More >

What’s new: Extension for Microsoft Dynamics NAV 2016

We all have seen the situation where we need to put in lot of efforts to modify the standard NAV obj...

Read More >

How to print Header and Details (Lines) in different pages of a RDLC Report in NAV 2013 R2

We usually print header and details section of a document on same page, what if we want to print on ...

Read More >

Introduction to AngularJS

                         In this bl...

Read More >

Introduction to Load Testing

 Well, before learning what is Load testing. Let us discuss briefly the performance testing.&nb...

Read More >

Share

Try DevOpSmartBoard Ultimate complete Azure DevOps End-to end reporting tool

Sign Up

  • Recent
  • Popular
  • Tag
Tags
Monthly Archive
Subscribe
Name

Text/HTML
Contact Us
  • *
  • *