7225: Add workflow badge to the readme

[thegreystone]

Trying a PR to see if it works.

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7225: Add workflow badge to the readme

Reviewers

• Henrik Dafgård (@Gunde - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/233/head:pull/233
$ git checkout pull/233

Update a local copy of the PR:
$ git checkout pull/233
$ git pull https://git.openjdk.java.net/jmc pull/233/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 233

View PR using the GUI difftool:
$ git pr show -t 233

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/233.diff

[bridgekeeper]

👋 Welcome back hirt! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (ad5cd5c1)

[openjdk]

@thegreystone This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7225: Add workflow badge to the readme

Reviewed-by: hdafgard

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 11 new commits pushed to the master branch:

• a2f6b15: 7046: Update to the 2021-03 platform
• f1a63ec: 7162: Stop using the chromium library based browser component
• 2e242ec: 7191: The release notes tool should be using JDK 8
• 1c008c3: 7205: Correct URL for Oracle's JMC production binaries
• 6149b48: 6890: defineEventProbes should throw exception on malformed probe definitions
• acbc1e6: 7158: [JFR Writer] Improve single-value types handling
• 2111820: 7156: [JFR Writer] Allow providing extra recording settings
• 20d8777: 7155: [JFR Writer] Complete the annotation handling code
• e97d985: 7154: [JFR Writer] Improve lazy evaluation of the type defining block
• c1937f1: 7139: Prepare new and noteworthy for JMC 8.0.0
• ... and 1 more: https://git.openjdk.java.net/jmc/compare/e52a3615738d10a75f7d0346b9302bcdf6f5acc8...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[thegreystone]

/integrate

[openjdk]

@thegreystone Since your change was applied there have been 11 commits pushed to the master branch:

• a2f6b15: 7046: Update to the 2021-03 platform
• f1a63ec: 7162: Stop using the chromium library based browser component
• 2e242ec: 7191: The release notes tool should be using JDK 8
• 1c008c3: 7205: Correct URL for Oracle's JMC production binaries
• 6149b48: 6890: defineEventProbes should throw exception on malformed probe definitions
• acbc1e6: 7158: [JFR Writer] Improve single-value types handling
• 2111820: 7156: [JFR Writer] Allow providing extra recording settings
• 20d8777: 7155: [JFR Writer] Complete the annotation handling code
• e97d985: 7154: [JFR Writer] Improve lazy evaluation of the type defining block
• c1937f1: 7139: Prepare new and noteworthy for JMC 8.0.0
• ... and 1 more: https://git.openjdk.java.net/jmc/compare/e52a3615738d10a75f7d0346b9302bcdf6f5acc8...master

Your commit was automatically rebased without conflicts.

Pushed as commit b46be35.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.