docs: update bitbucket cloud docs for api tokens by zakisk · Pull Request #2501 · tektoncd/pipelines-as-code

zakisk · 2026-02-23T18:50:33Z

this commit updates bitbucket cloud docs about replacement of app passwords with api tokens and adds a guide on how to create api token.

📝 Description of the Change

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

Fixes #

🚀 Type of Change

🧪 Testing Strategy

🤖 AI Assistance

I have not used any AI assistance for this PR.
I have used AI assistance for this PR.

If you have used AI assistance, please provide the following details:

Which LLM was used?

Extent of AI Assistance:

Documentation and research only
Unit tests or E2E tests only
Code generation (parts of the code)
Full code generation (most of the PR)
PR description and comments
Commit message(s)

Important

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Gemini gemini@google.com
Co-authored-by: ChatGPT noreply@chatgpt.com
Co-authored-by: Claude noreply@anthropic.com
Co-authored-by: Cursor noreply@cursor.com
Co-authored-by: Copilot Copilot@users.noreply.github.com

**💡You can use the script ./hack/add-llm-coauthor.sh to automatically add
these co-author trailers to your commits.

✅ Submitter Checklist

gemini-code-assist · 2026-02-23T18:50:48Z

Summary of Changes

Hello @zakisk, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Bitbucket Cloud installation documentation to reflect the deprecation of App Passwords and the transition to API Tokens. It provides comprehensive guidance on how to create and configure API Tokens, along with necessary permission settings. Additionally, it clarifies that the user field in the Repository Custom Resource should now use the Atlassian email ID.

Highlights

Bitbucket Cloud App Password Deprecation: Bitbucket Cloud is deprecating App Passwords, with all existing ones to be disabled by June 9, 2026. The documentation now reflects this change, providing a warning about the upcoming deprecation.
API Token Guidance: New instructions have been added for creating Bitbucket API Tokens, including a link to Atlassian's guide and a list of required permissions (read:workspace, read:pullrequest, read:repository, write:repository) for integration with Pipelines-as-Code.
Repository CR 'user' field update: The user field in the Repository Custom Resource (CR) now requires the Bitbucket/Atlassian account email address instead of the username, aligning with the shift to API tokens. The documentation includes guidance on how to find this email.

Changelog

docs/content/docs/install/bitbucket_cloud.md
- Added a warning about the deprecation of Bitbucket Cloud App Passwords.
- Provided a new section with instructions for creating Bitbucket API Tokens.
- Updated the required permissions for Bitbucket integration to align with API Tokens.
- Clarified that the user field in the Repository CR should now use the Atlassian email ID.
- Replaced the old screenshot for username settings with a new one for account settings to find the email ID.

Activity

No specific activity (comments, reviews, progress updates) has been recorded for this pull request since its creation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

pipelines-as-code · 2026-02-23T18:50:55Z

🔍 PR Lint Feedback

Note: This automated check helps ensure your PR follows our contribution guidelines.

⚠️ Items that need attention:

🎫 Jira reference

Add a Jira reference in the description using one of the following formats:

https://issues.redhat.com/browse/SRVKP-<number>

If no SRVKP ticket exists yet, link a GitHub issue instead (e.g., Fixes #123).
Minor housekeeping PRs without Jira coverage can skip this after confirming with reviewers.

🤖 AI attribution

The following commits lack an explicit AI attribution footer:

b07a42b docs: update bitbucket cloud docs for api tokens

If no AI assistance was used for a commit, you can ignore this warning.
Otherwise add an Assisted-by: or Co-authored-by: footer referencing the AI used.

ℹ️ Next Steps

Review and address the items above
Push new commits to update this PR
This comment will be automatically updated when issues are resolved

🔧 Admin Tools (click to expand)

Automated Issue/Ticket Creation:

/issue-create - Generate a GitHub issue from this PR content using AI
/jira-create - Create a SRVKP Jira ticket from this PR content using AI

⚠️ Important: Always review and edit generated content before finalizing tickets/issues.
The AI-generated content should be used as a starting point and may need adjustments.

These commands are available to maintainers and will post the generated content as PR comments for review.

_{🤖 This feedback was generated automatically by the PR CI system}

gemini-code-assist

Code Review

This pull request updates the Bitbucket Cloud documentation to reflect the deprecation of app passwords and the transition to API tokens. The changes include instructions on how to create API tokens and clarify the use of the Atlassian email ID in the user field of the Repository CR. Overall, the updates are crucial for keeping the documentation current with Bitbucket Cloud's authentication changes. I've provided feedback on improving the presentation of the deprecation notice and adhering to the documentation style guide regarding hint blocks.

gemini-code-assist · 2026-02-23T18:52:49Z

docs/content/docs/install/bitbucket_cloud.md

+{{< hint danger >}}

-<https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/>
+App passwords are now replaced with [API Tokens](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/), you cannot create a new app password now and All existing app passwords will be disabled on June 9, 2026.

-Check these boxes to add the permissions to the token:
+{{< /hint >}}


The general rules for this repository state to "Avoid using 'hint' blocks in documentation." While the information about app password deprecation is crucial, it should be integrated directly into the text rather than using a hint danger block.

Suggested change

{{< hint danger >}}

<https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/>

App passwords are now replaced with [API Tokens](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/), you cannot create a new app password now and All existing app passwords will be disabled on June 9, 2026.

Check these boxes to add the permissions to the token:

{{< /hint >}}

App passwords are now replaced with [API Tokens](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/). You cannot create a new app password, and all existing app passwords will be disabled on June 9, 2026.

References

Avoid using 'hint' blocks in documentation.

just mentions that we only support api token since app password is deprecated, don't phrsae in the "now" tense, it's a documentation not a changelog..

gemini-code-assist · 2026-02-23T18:52:50Z

docs/content/docs/install/bitbucket_cloud.md

 Follow the Pipelines-as-Code [installation](/docs/install/installation) according to your Kubernetes cluster.

-## Create Bitbucket Cloud App Password
+## Bitbucket Cloud App Password


The heading "Bitbucket Cloud App Password" is immediately followed by a deprecation notice. It would improve clarity to combine the content into a single section focused on API Tokens, with a clear deprecation note for app passwords at the beginning of that section. Consider renaming this section to reflect the deprecation or integrating its content into the "Create Bitbucket API Token" section.

Suggested change

## Bitbucket Cloud App Password

## Bitbucket Cloud Authentication

chmouel · 2026-02-24T09:56:21Z

docs/content/docs/install/bitbucket_cloud.md

+## Bitbucket Cloud App Password

-Follow this guide to create an app password:
+App passwords are replaced with [API Tokens](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/). You cannot create a new app password, and all existing app passwords will be disabled on June 9, 2026.


why mentioning date, they go out of date quickly, just mentions that it is not supported since not supported by bitbucket anymore, this should not be complicated..

as users are using app passwords so far we should let them know that they wouldn't work after that date and we will remove this after that date. because someone might be having app passwords so let them know that it won't work and PaC supports API tokens

docs/content/docs/install/bitbucket_cloud.md

this commit updates bitbucket cloud docs about replacement of app passwords with api tokens and adds a guide on how to create api token. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

chmouel · 2026-02-25T12:33:00Z

/lgtm

pipelines-as-code

Congrats @zakisk your PR Has been approved 🎉

✅ Pull Request Approved

Approval Status:

Required Approvals: 1
Current Approvals: 1

👥 Reviewers Who Approved:

Reviewer	Permission Level	Approval Status
@chmouel	`admin`	✅

📝 Next Steps

Ensure all required checks pass
Comply with branch protection rules
Request a maintainer to merge using the /merge command (or merge it
directly if you have repository permission).

Automated by the PAC Boussole 🧭

pipelines-as-code bot added documentation Improvements or additions to documentation providers labels Feb 23, 2026

gemini-code-assist bot reviewed Feb 23, 2026

View reviewed changes

zakisk force-pushed the update-bb-cloud-docs-for-tokens branch from 5ce9f41 to eb298e8 Compare February 24, 2026 06:45

pipelines-as-code bot added the bitbucket-datacenter label Feb 24, 2026

chmouel reviewed Feb 24, 2026

View reviewed changes

docs/content/docs/install/bitbucket_cloud.md Outdated Show resolved Hide resolved

zakisk force-pushed the update-bb-cloud-docs-for-tokens branch from eb298e8 to 41dfb06 Compare February 24, 2026 18:58

docs: update bitbucket cloud docs for api tokens

b07a42b

this commit updates bitbucket cloud docs about replacement of app passwords with api tokens and adds a guide on how to create api token. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

zakisk force-pushed the update-bb-cloud-docs-for-tokens branch from 41dfb06 to b07a42b Compare February 25, 2026 12:32

pipelines-as-code bot approved these changes Feb 25, 2026

View reviewed changes

zakisk merged commit ec55549 into tektoncd:main Feb 25, 2026
5 checks passed

zakisk deleted the update-bb-cloud-docs-for-tokens branch February 25, 2026 12:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: update bitbucket cloud docs for api tokens#2501

docs: update bitbucket cloud docs for api tokens#2501
zakisk merged 1 commit intotektoncd:mainfrom
zakisk:update-bb-cloud-docs-for-tokens

zakisk commented Feb 23, 2026

Uh oh!

gemini-code-assist bot commented Feb 23, 2026

Uh oh!

pipelines-as-code bot commented Feb 23, 2026 •

edited

Loading

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 23, 2026

Uh oh!

chmouel Feb 23, 2026

Uh oh!

chmouel Feb 23, 2026

Uh oh!

gemini-code-assist bot Feb 23, 2026

Uh oh!

chmouel Feb 24, 2026

Uh oh!

zakisk Feb 24, 2026

Uh oh!

Uh oh!

chmouel commented Feb 25, 2026

Uh oh!

pipelines-as-code bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	## Bitbucket Cloud App Password
	## Bitbucket Cloud Authentication

Conversation

zakisk commented Feb 23, 2026

📝 Description of the Change

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

🚀 Type of Change

🧪 Testing Strategy

🤖 AI Assistance

✅ Submitter Checklist

Uh oh!

gemini-code-assist bot commented Feb 23, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

pipelines-as-code bot commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 PR Lint Feedback

⚠️ Items that need attention:

🎫 Jira reference

🤖 AI attribution

ℹ️ Next Steps

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

chmouel Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

chmouel Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

chmouel Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

zakisk Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

chmouel commented Feb 25, 2026

Uh oh!

pipelines-as-code bot left a comment

Choose a reason for hiding this comment

✅ Pull Request Approved

👥 Reviewers Who Approved:

📝 Next Steps

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

pipelines-as-code bot commented Feb 23, 2026 •

edited

Loading