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

Add bluesky post plugin #4549

Merged
merged 5 commits into from
Jan 28, 2025
Merged

Conversation

anbraten
Copy link
Member

No description provided.

@anbraten anbraten added the documentation docu & docs label Dec 10, 2024
@woodpecker-bot
Copy link
Contributor

woodpecker-bot commented Dec 10, 2024

Deployment of preview was torn down

@qwerty287
Copy link
Contributor

Why is it not verified?

@anbraten
Copy link
Member Author

Why is it not verified?

Probably as someone said there are too many official plugins.

@qwerty287
Copy link
Contributor

Yes, I say this, but just changing the verified value doesn't change that. In that case, the plugin should live under your personal account and not under the woodpecker-plugins org. At least that's what I thinl

@pat-s
Copy link
Contributor

pat-s commented Dec 22, 2024

If anbraten wants to maintain it and puts his name into CODEOWNERS and possibly the README, I think it can live there.

We still don't have a clear rule for where plugins should live WRT to ownership and maintenance.
One approach could be to say that only maitainers can host plugins in the CB org. But then again, if a maintainer drops out, the plugin stays within the org and someone has to maintain it. Guess there will never be a "perfect" solution.

Copy link
Contributor

@pat-s pat-s left a comment

Choose a reason for hiding this comment

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

I think we have two options here:

  • "verfiedi" + CB org
  • "unverified" + personal username

I'd let @anbraten decide what he wants to do?

@xoxys
Copy link
Member

xoxys commented Jan 12, 2025

This is pending for weeks now, @anbraten @qwerty287 what to do now?

@qwerty287
Copy link
Contributor

I'd say either make it verified or change the repo owner.

@xoxys
Copy link
Member

xoxys commented Jan 13, 2025

Yeah, but moving the repo to another account requires participation by anbraten and there was no response since a month now. So we can either close this PR or change it to verified and merge it. To be honest, I would just close this PR for now.

@qwerty287
Copy link
Contributor

If it will stay in the woodpecker-plugins org it should be listed as verified in the list I think. So if we close this now, it should be added later as verified or moved away from the org as well.

@xoxys
Copy link
Member

xoxys commented Jan 13, 2025

Alright... Then I'll change it to verified now, even if I don't like it and already see no activity on the plugin.

@qwerty287 qwerty287 requested a review from xoxys January 28, 2025 10:30
Copy link
Member

@xoxys xoxys left a comment

Choose a reason for hiding this comment

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

Thanks

@qwerty287 qwerty287 requested a review from xoxys January 28, 2025 10:35
@qwerty287 qwerty287 merged commit ee0e5fb into woodpecker-ci:main Jan 28, 2025
7 checks passed
@woodpecker-bot woodpecker-bot mentioned this pull request Jan 28, 2025
1 task
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.

5 participants