Advertise project access tokens as default instead of user-wide access tokens

DracoBlue commented 8 months ago

Checklist

[x] I've read and followed the Contribution Guidelines
[x] step.yml and README.md is updated with the changes (if needed)

Version

Context

The current documentation expects people to provide their user wide access token for gitlab. But the step also works seamlessly with project wide access tokens (which are 100% sufficient for what this step does).

Changes

Add details how to generate a project access token. Listing user tokens as second option how to retrieve one.

Investigation details

I tested the step on my production project with a project access token and it worked flawlessly. There are no code changes necessary.

Decisions

Advertise the project access token generation before user access token because the user one is too powerful to be stored in projects. And if the colleague leaves and the account in gitlab is blocked, your bitrise process will not work anymore.

DracoBlue commented 7 months ago

ping @bitrise-coresteps-bot

en-jschuetze commented 5 months ago

any updates?

bitrise-steplib / steps-gitlab-status