Skip to content

Commit bad2228

Browse files
authored
Merge pull request #2588 from MikeRalphson/codetriage
docs: add CodeTriage badge and CTA to README.md
2 parents 12f1646 + 44dc747 commit bad2228

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The OpenAPI Specification
22

3-
![Build Status](https://github.com/OAI/OpenAPI-Specification/workflows/validate-markdown/badge.svg)
3+
![Build Status](https://github.com/OAI/OpenAPI-Specification/workflows/validate-markdown/badge.svg) [![Issue triagers](https://www.codetriage.com/oai/openapi-specification/badges/users.svg)](https://www.codetriage.com/oai/openapi-specification)
44

55
![](https://avatars3.githubusercontent.com/u/16343502?v=3&s=200)
66

@@ -47,6 +47,7 @@ The OpenAPI Initiative encourages participation from individuals and companies a
4747
* Review the [current specification](versions/3.1.0.md). The human-readable markdown file _is the source of truth_ for the specification.
4848
* Review the [development](DEVELOPMENT.md) process so you understand how the spec is evolving.
4949
* Check the [issues](https://github.com/OAI/OpenAPI-Specification/issues) and [pull requests](https://github.com/OAI/OpenAPI-Specification/pulls) to see if someone has already documented your idea or feedback on the specification. You can follow an existing conversation by subscribing to the existing issue or PR.
50+
* Subscribe to an open issue a day (or a week) in your inbox via [CodeTriage.com](https://www.codetriage.com/oai/openapi-specification).
5051
* Create an issue to describe a new concern. If possible, propose a solution.
5152

5253
Not all feedback can be accommodated and there may be solid arguments for or against a change being appropriate for the specification.

0 commit comments

Comments
 (0)