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

User Secrets #1739

Closed
4 tasks done
JakobDev opened this issue May 5, 2023 · 5 comments · Fixed by #2126
Closed
4 tasks done

User Secrets #1739

JakobDev opened this issue May 5, 2023 · 5 comments · Fixed by #2126
Labels
feature add new functionality
Milestone

Comments

@JakobDev
Copy link

JakobDev commented May 5, 2023

Clear and concise description of the problem

I have multiple Personal Projects which share the same Secrets. I have to configure the Secrets for each Project. It would be better to have Secrets on a User Level.

Suggested solution

We already have Secrets on Global and Organisation Level Level. Why not on a User Level?

Alternative

No response

Additional context

No response

Validations

  • Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
  • Read the Contributing Guidelines.
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@JakobDev JakobDev added the feature add new functionality label May 5, 2023
@6543
Copy link
Member

6543 commented May 7, 2023

user level in form of "for all user repos" for <user>/* repos ... or for all repos where the pipeline is run because of an user action ?!?

@JakobDev
Copy link
Author

JakobDev commented May 8, 2023

user level in form of "for all user repos" for <user>/* repos

Exact that. I have on Codeberg multiple Projects which deploy a Package to PyPI on a new Release, so it would be helpful if I can enter my credentials just once and not for each Project new.

@qwerty287
Copy link
Contributor

That's really easy as everything's there already. Just allow this on users too, back end is the same for orgs

@qwerty287 qwerty287 added the good first issue Likely to be an easy fix label May 8, 2023
@JakobDev
Copy link
Author

JakobDev commented May 9, 2023

Could you create A PR, so I don't have to setup a develop environment for this?

@laurivosandi
Copy link

I bumped into same issue. With everything set up GitHub I get Error getting membership for "laurivosandi". GET https://api.github.com/orgs/laurivosandi/memberships/laurivosandi: 404 NotFound []

qwerty287 added a commit that referenced this issue Aug 3, 2023
Make the user settings tabbed as well, currently only holding "Settings"
(language) and "API". Can be extended with user secrets (#1739) etc.
later.
![Screenshot 2023-08-02 at 09-56-00
Woodpecker](https://github.com/woodpecker-ci/woodpecker/assets/80460567/15d82800-8a4d-47fe-aa77-33462f63585e)
![Screenshot 2023-08-02 at 09-56-05
Woodpecker](https://github.com/woodpecker-ci/woodpecker/assets/80460567/de2640be-144c-4190-adb6-56d43a38bdda)

---------

Co-authored-by: Robert Kaussow <xoxys@rknet.org>
@qwerty287 qwerty287 added this to the 1.1.0 milestone Aug 5, 2023
@qwerty287 qwerty287 removed the good first issue Likely to be an easy fix label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature add new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants