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

Read Project and Repository Categories #319

Open
krasv opened this issue Jan 3, 2022 · 4 comments · May be fixed by #320
Open

Read Project and Repository Categories #319

krasv opened this issue Jan 3, 2022 · 4 comments · May be fixed by #320

Comments

@krasv
Copy link
Contributor

krasv commented Jan 3, 2022

Bitbucket provides a "hidden" feature for adding and reusing categories at projects and repositories.
This categories can be read by a dedicated add on REST API.

Expected Behavior

Endpoints at the ProjectAPI and the RepositoryAPI.

Current Behavior

not implemented yet.

Context

I need to get this information, since we put a lot of meta information into that categories in our bitbucket.

Steps to Reproduce (for bugs)

Your Environment

@krasv krasv linked a pull request Jan 3, 2022 that will close this issue
@cdancy
Copy link
Owner

cdancy commented Jan 14, 2022

Does Bitbucket provide this feature or Communardo?

@krasv
Copy link
Contributor Author

krasv commented Jan 15, 2022

As commented at the PR: the API comes with the add-on and extends the basic api.

@krasv
Copy link
Contributor Author

krasv commented Feb 2, 2022

Hi Christopher,

any thoughts here? May I go forward with the extension or do you reject the changes?

regards
Sven

@cdancy
Copy link
Owner

cdancy commented Feb 14, 2022

@krasv apologies for getting back so late. Been busy with work. I don't want anything provider specific within this library. Developers are free to fork this project however and add in their own implementations/plugins/etc.

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

Successfully merging a pull request may close this issue.

2 participants