Commit e846623
authored
NO-JIRA: Update OWNERS (#83)
<!--
- Please ensure code changes are split into a series of logically
independent commits.
- Every commit should have a subject/title (What) and a description/body
(Why).
- Every PR must have a description.
- As an example you can use git commit -m"What" -m"Why" to achieve the
requirements above.
GitHub automatically recognizes the commit description (-m"Why") in
single commit PRs and
adds it as the PR description.
- Use the [imperative
mood](https://en.wikipedia.org/wiki/Imperative_mood) in the subject line
for every commit. E.g `Mark infraID as required` instead of `This patch
marks infraID as required`
(This follows Git’s own built-in conventions). See
openshift/hypershift#485
as an example.
- See
https://github.com/redhat-openshift-ecosystem/opct/blob/main/CONTRIBUTING.md
for more details.
Delete this text before submitting the PR.
-->
**What this PR does / why we need it**:
**Which issue(s) this PR fixes** *(optional, use `fixes
#<issue_number>(, fixes #<issue_number>, ...)` format, where
issue_number might be a GitHub issue, or a Jira story*:
Fixes #
**Checklist**
- [ ] Subject and description added to both, commit and PR.
- [ ] Relevant issues have been referenced.
- [ ] This change includes docs.
- [ ] This change includes unit tests.1 parent 1cefc3c commit e846623
1 file changed
+0
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
8 | 7 | | |
9 | 8 | | |
10 | 9 | | |
11 | 10 | | |
12 | 11 | | |
13 | 12 | | |
14 | | - | |
15 | 13 | | |
0 commit comments