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 Cameron Rushton to CODEOWNERS #89

Merged
merged 1 commit into from Oct 19, 2021

Conversation

damaru-inc
Copy link
Contributor

Description

This is a request to add Cameron Rushton to CODEOWNERS.

@sonarcloud
Copy link

sonarcloud bot commented Oct 18, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@derberg
Copy link
Member

derberg commented Oct 18, 2021

@damaru-inc please change title as such change should not really trigger a release to npm

@CameronRushton please approve

@damaru-inc @fmvilas should me and Fran stay in the file, maybe we should step down?

@damaru-inc
Copy link
Contributor Author

What change should I make to the title so that it passes the Lint test? I thought it had to start with fix: or feat: or something like that.

As for removing you and Fran, I'll leave that up to you.

@derberg
Copy link
Member

derberg commented Oct 18, 2021

@damaru-inc damaru-inc changed the title fix: add Cameron Rushton to CODEOWNERS chore: add Cameron Rushton to CODEOWNERS Oct 18, 2021
@damaru-inc
Copy link
Contributor Author

Thanks, I was having trouble finding that document...

@fmvilas
Copy link
Member

fmvilas commented Oct 18, 2021

Yeah, I don't think I deserve to be a maintainer of this repo, I've never made any contribution as far as I remember 🤔 Happy to help though.

Copy link
Member

@CameronRushton CameronRushton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phew. Guess it's time for me to get a little more serious about keeping up to date with this repo!

@derberg
Copy link
Member

derberg commented Oct 19, 2021

@fmvilas I think it is better if we are removed to give more freedom to folks and if ever needed, some second opinion or special review, they can always count on us.

@damaru-inc I say you remove us

@fmvilas
Copy link
Member

fmvilas commented Oct 19, 2021

Yeah, go ahead and remove us. We also have to be fair and we didn't do any merits to be maintainers of this repo :)

@damaru-inc
Copy link
Contributor Author

That's fine, but could one of you please approve this PR first, so that Cameron can approve my other PR? Then I'll remove you. Thanks!

@derberg
Copy link
Member

derberg commented Oct 19, 2021

@damaru-inc you can remove us now, and I will merge as Admin

@damaru-inc damaru-inc merged commit 79891ff into asyncapi:master Oct 19, 2021
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 0.2.11 🎉

The release is available on:

Your semantic-release bot 📦🚀

@derberg
Copy link
Member

derberg commented Oct 19, 2021

@damaru-inc I think you forgot about the proper prefix in the commit message 😄

@damaru-inc
Copy link
Contributor Author

damaru-inc commented Oct 19, 2021

Doh! You're right, I just fixed the PR title. But that's not what's causing the issue of us not being able to merge the other PR, is it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants