Skip to content

Commit

Permalink
Update CI badge in README
Browse files Browse the repository at this point in the history
  • Loading branch information
GordStephen committed Nov 28, 2024
1 parent fe0a56b commit 8fcfaa7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# MinCostFlows

[![Build Status](https://travis-ci.org/NREL/MinCostFlows.jl.svg?branch=master)](https://travis-ci.org/NREL/MinCostFlows.jl)
[![Coverage Status](https://coveralls.io/repos/github/NREL/MinCostFlows.jl/badge.svg?branch=master)](https://coveralls.io/github/NREL/MinCostFlows.jl?branch=master)
[![Tests](https://github.com/NREL/MinCostFlows.jl/actions/workflows/CI.yml/badge.svg)](https://github.com/NREL/MinCostFlows.jl/actions/workflows/CI.yml)
[![Coverage](https://codecov.io/gh/NREL/MinCostFlows.jl/graph/badge.svg?token=QhINmAOLgW)](https://codecov.io/gh/NREL/MinCostFlows.jl)

Efficiently solves min-cost network flow problems using the Relaxation
dual ascent method of Bertsekas (1985), including support for parameter
Expand Down

2 comments on commit 8fcfaa7

@GordStephen
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/120355

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.2 -m "<description of version>" 8fcfaa73a7b22fada04b272db164016a340e840a
git push origin v0.1.2

Also, note the warning: This looks like a new registration that registers version 0.1.2.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Please sign in to comment.