Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add Veepee into USERS #13301

Merged
merged 2 commits into from
May 22, 2023
Merged

chore: Add Veepee into USERS #13301

merged 2 commits into from
May 22, 2023

Conversation

nerzhul
Copy link
Contributor

@nerzhul nerzhul commented Apr 20, 2023

Add Veepee in users

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

@nerzhul nerzhul force-pushed the patch-1 branch 2 times, most recently from aa42d81 to 74f23b6 Compare April 20, 2023 11:45
@nerzhul nerzhul changed the title add Veepee in USERS chore: Add Veepee into USERS Apr 20, 2023
Signed-off-by: Loïc Blot <nerzhul@users.noreply.github.com>
@codecov
Copy link

codecov bot commented Apr 20, 2023

Codecov Report

Patch coverage has no change and project coverage change: +0.15 🎉

Comparison is base (ceed653) 49.01% compared to head (2438f96) 49.17%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #13301      +/-   ##
==========================================
+ Coverage   49.01%   49.17%   +0.15%     
==========================================
  Files         247      248       +1     
  Lines       42685    42871     +186     
==========================================
+ Hits        20924    21083     +159     
- Misses      19645    19687      +42     
+ Partials     2116     2101      -15     

see 18 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

USERS.md Outdated Show resolved Hide resolved
@nerzhul
Copy link
Contributor Author

nerzhul commented May 22, 2023

@blakepettersson fixed

@alexmt alexmt merged commit b44c805 into argoproj:master May 22, 2023
@nerzhul nerzhul deleted the patch-1 branch June 23, 2023 12:39
yyzxw pushed a commit to yyzxw/argo-cd that referenced this pull request Aug 9, 2023
* chore: Add Veepee into USERS

Signed-off-by: Loïc Blot <nerzhul@users.noreply.github.com>

* fix: indent

---------

Signed-off-by: Loïc Blot <nerzhul@users.noreply.github.com>
tesla59 pushed a commit to tesla59/argo-cd that referenced this pull request Dec 16, 2023
* chore: Add Veepee into USERS

Signed-off-by: Loïc Blot <nerzhul@users.noreply.github.com>

* fix: indent

---------

Signed-off-by: Loïc Blot <nerzhul@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants