actions/ai-inference
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Apply markdown lint fixes

Browse Source
This commit is contained in:
Sean Goedecke
2025-04-07 00:55:53 +00:00
parent 35e73ae13f
commit e7e793aa37
2 changed files with 14 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CODE_OF_CONDUCT.md
+10 -9
View File
@@ -48,18 +48,19 @@ offensive, or harmful.
This Code of Conduct applies within all project spaces, and it also applies when This Code of Conduct applies within all project spaces, and it also applies when
an individual is representing the project or its community in public spaces. an individual is representing the project or its community in public spaces.
Examples of representing a project or community include using an official Examples of representing a project or community include using an official
project e-mail address, posting via an official social media account, or acting project email address, posting via an official social media account, or acting
as an appointed representative at an online or offline event. Representation of as an appointed representative at an online or offline event. Representation of
a project may be further defined and clarified by project maintainers. a project may be further defined and clarified by project maintainers.
## Enforcement ## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at opensource@github.com. All complaints reported by contacting the project team at `opensource@github.com`. All
will be reviewed and investigated and will result in a response that is deemed complaints will be reviewed and investigated and will result in a response that
necessary and appropriate to the circumstances. The project team is obligated to is deemed necessary and appropriate to the circumstances. The project team is
maintain confidentiality with regard to the reporter of an incident. Further obligated to maintain confidentiality with regard to the reporter of an
details of specific enforcement policies may be posted separately. incident. Further details of specific enforcement policies may be posted
separately.
Project maintainers who do not follow or enforce the Code of Conduct in good Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other faith may face temporary or permanent repercussions as determined by other
@@ -69,9 +70,9 @@ members of the project's leadership.
This Code of Conduct is adapted from the [Contributor Covenant][homepage], This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at version 1.4, available at
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html `https://www.contributor-covenant.org/version/1/4/code-of-conduct.html`
[homepage]: https://www.contributor-covenant.org [homepage]: `https://www.contributor-covenant.org`
For answers to common questions about this code of conduct, see For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq `https://www.contributor-covenant.org/faq`
CONTRIBUTING.md
+4 -4
View File
@@ -1,4 +1,4 @@
## Contributing # Contributing
[fork]: https://github.com/actions/ai-inference/fork [fork]: https://github.com/actions/ai-inference/fork
[pr]: https://github.com/actions/ai-inference/compare [pr]: https://github.com/actions/ai-inference/compare
@@ -47,7 +47,7 @@ avoid having to include the `node_modules/` directory in the repository.
`npm run test` `npm run test`
1. Make sure your code is correctly formatted: `npm run format` 1. Make sure your code is correctly formatted: `npm run format`
1. Update `dist/index.js` using `npm run build`. This creates a single 1. Update `dist/index.js` using `npm run build`. This creates a single
javascript file that is used as an entrypoint for the action JavaScript file that is used as an entrypoint for the action
1. Push to your fork and [submit a pull request][pr] 1. Push to your fork and [submit a pull request][pr]
1. Pat yourself on the back and wait for your pull request to be reviewed and 1. Pat yourself on the back and wait for your pull request to be reviewed and
merged. merged.
@@ -66,7 +66,7 @@ All the concepts from
[the actions/toolkit release docs](https://github.com/actions/toolkit/blob/main/docs/action-versioning.md) [the actions/toolkit release docs](https://github.com/actions/toolkit/blob/main/docs/action-versioning.md)
apply. Please read that first! apply. Please read that first!
Once the changes are merged into main, a repo maintainer should: Once the changes are merged into main, a repository maintainer should:
1. Bump the package version by running 1. Bump the package version by running
[`npm version [major|minor|patch]`](https://docs.npmjs.com/cli/v7/commands/npm-version). [`npm version [major|minor|patch]`](https://docs.npmjs.com/cli/v7/commands/npm-version).
@@ -80,7 +80,7 @@ Once the changes are merged into main, a repo maintainer should:
the specific ref of the release you just made. For example, if we just the specific ref of the release you just made. For example, if we just
released `v1.1.0`, we would rewrite the `v1` tag like this: released `v1.1.0`, we would rewrite the `v1` tag like this:
``` ```bash
git tag -fa v1 v1.1.0 -m "Update v1 tag to point to v1.1.0" git tag -fa v1 v1.1.0 -m "Update v1 tag to point to v1.1.0"
git push origin v1 --force git push origin v1 --force
``` ```