Skip to content

Conversation

xiaomaogy
Copy link
Contributor

Proposed change(s)

Updated the link for the badge to point to the newer version

Useful links (Github issues, JIRA tickets, ML-Agents forum threads etc.)

Types of change(s)

  • Bug fix
  • New feature
  • Code refactor
  • Breaking change
  • Documentation update
  • Other (please describe)

Checklist

  • Added tests that prove my fix is effective or that my feature works
  • Updated the changelog (if applicable)
  • Updated the documentation (if applicable)
  • Updated the migration guide (if applicable)

Other comments

@xiaomaogy xiaomaogy requested a review from vincentpierre June 17, 2020 00:16
@chriselion
Copy link
Contributor

I updated the release checklist - we should be updating any release_*_docs links in each release.

Copy link
Contributor

@chriselion chriselion left a comment

Choose a reason for hiding this comment

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

Could you search the code for all instances of release_2_docs and replace it with release_3_docs? The only exception (I think) should be the table with all of the releases.

@xiaomaogy xiaomaogy requested a review from chriselion June 17, 2020 05:43
@xiaomaogy xiaomaogy merged commit 3d2204d into master Jun 17, 2020
@delete-merged-branch delete-merged-branch bot deleted the develop-badge-version branch June 17, 2020 19:08
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants