Configuring Lead Time for Changes in a Github integration

The Lead Time for Changes is a Dora Metric that
aims to measure the speed of code or software deployment, from the
closure of a product release to its arrival in the production
environment. This metric helps to better understand the cycle of
solutions created by your team, ensuring that they are executed as
quickly as possible.

To measure the speed, it’s essential to know when the demand was
identified and the time invested in its execution. In addition to
helping reduce the response time to fix issues in an application, the
Lead Time for Changes facilitates the automation of implementation and
improves the release process. Organizing smaller and more frequent
releases tends to continuously improve quality. A Lead Time occurs when a
merge is performed on the target branch, when this occurs it looks at
all the commits that are in the merge and checks the range of the merge
date with the date of the oldest commit. This is for each merge event
carried out in the target branch. The platform displays the simple
average of the last 30 days (total sum of Lead Times / number of Lead
Time).

To set up the Lead Time for Changes metric in the One Platform, follow these steps:

  1. Access the integrations page, located in the left sidebar menu under the “Integrations” tab.
  2. Choose whether you want to integrate via Github or Bitbucket.
  3. Click on “Install new integration” to initiate the integration process.





After clicking to install the new
integration, the window will be redirected to Github. You’ll need to log
in to your Github account, and once you are logged in, choose an
organization to install our application. It’s essential to note that
currently, we only offer compatibility with Github organizations, and
personal accounts will not work for this integration.



After choosing the organization, a configuration screen will be
displayed. You can choose to install the application in all repositories
by selecting “All repositories” or opt to install it in specific
repositories by choosing “Only select repositories.” If you decide to
select repositories



Once you have chosen the best
option for you, click on “Install.” After installing our application on
Github, you will be redirected to the integration screen, where you can
connect applications with repositories.



Connecting applications with repositories:

To associate a repository in your organization with an application,
click on the green button called “Connect application” and you will be
directed to a configuration screen. Here, you need to follow these
steps:

  1. Choose the product to connect with the application in the “Choose product” field (optional)
  2. Select the application within this product in the “Choose application” field.
  3. Choose the integration to be used in the “Choose integration” field.
  4. Select the repository of the chosen integration that you want to
    associate with this application in the “Choose repository” field. Note
    that it is one repository per application.

After making choices in these fields, you need to specify the target
branch. Selecting the target branch is essential because it must be the
main branch of the repository, usually called “main” or “master”. The
platform will receive pull requests that will be merged into this
agency, and this is where Lead Times for Changes will be calculated.
When combining this branch, make sure it looks exactly as it appears on
Github.

After completing the configurations, click “Complete integration” to
finalize the connection between the application and the chosen
repository.

Once you’ve completed the configurations, click on “Finish
integration” to finalize the connection between the application and the
chosen repository.



 The value of the Lead Time for
Changes will appear on the page of the associated application within the
chosen product. You can find this value, calculated based on the last
30 days, in the last box on the right side of your screen.

 

To unlink an application, follow these steps:

  1. Go to the desired associated application.
  2. Click on the button with the pencil icon to enter the edit mode, and a editing box will appear.
  3. Look for the application you want to unlink within the editing box.
  4. Click on the button with the trash bin icon next to the application you want to unlink.
  5. After the confirmation prompt appears, click on “Delete connection” to unlink the application.





Deleting the integration can be done directly through github, click the button with this you will be redirected to github, go down the page, in Danger zone click on Uninstall 


The Lead Time for Changes is a Dora Metric that
aims to measure the speed of code or software deployment, from the
closure of a product release to its arrival in the production
environment. This metric helps to better understand the cycle of
solutions created by your team, ensuring that they are executed as
quickly as possible.

To measure the speed, it’s essential to know when the demand was
identified and the time invested in its execution. In addition to
helping reduce the response time to fix issues in an application, the
Lead Time for Changes facilitates the automation of implementation and
improves the release process. Organizing smaller and more frequent
releases tends to continuously improve quality. A Lead Time occurs when a
merge is performed on the target branch, when this occurs it looks at
all the commits that are in the merge and checks the range of the merge
date with the date of the oldest commit. This is for each merge event
carried out in the target branch. The platform displays the simple
average of the last 30 days (total sum of Lead Times / number of Lead
Time).

To set up the Lead Time for Changes metric in the One Platform, follow these steps:

  1. Access the integrations page, located in the left sidebar menu under the “Integrations” tab.
  2. Choose whether you want to integrate via Github or Bitbucket.
  3. Click on “Install new integration” to initiate the integration process.





After clicking to install the new
integration, the window will be redirected to Github. You’ll need to log
in to your Github account, and once you are logged in, choose an
organization to install our application. It’s essential to note that
currently, we only offer compatibility with Github organizations, and
personal accounts will not work for this integration.



After choosing the organization, a configuration screen will be
displayed. You can choose to install the application in all repositories
by selecting “All repositories” or opt to install it in specific
repositories by choosing “Only select repositories.” If you decide to
select repositories



Once you have chosen the best
option for you, click on “Install.” After installing our application on
Github, you will be redirected to the integration screen, where you can
connect applications with repositories.