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.

Sign up for GitHub

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

Jump to bottom

Octotree support. #3045

Closed
lunny opened this issue Dec 1, 2017 · 7 comments
Closed

Octotree support. #3045

lunny opened this issue Dec 1, 2017 · 7 comments
Labels
status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. type/upstream This is an issue in one of Gitea's dependencies and should be reported there

Comments

@lunny
Copy link
Member

lunny commented Dec 1, 2017

see https://github.com/buunguyen/octotree, currently octotree will visit /api/v3 but not /api/v1.
@lunny lunny added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Dec 1, 2017
@lunny
Copy link
Member Author

lunny commented Dec 1, 2017

Add an issue on that repository ovity/octotree#467

@sapk
Copy link
Member

sapk commented Dec 1, 2017

We could try to setup a v3 api and re-use func of v1 that are compatible and for the rest add it to the todo list ?

@lafriks
Copy link
Member

lafriks commented Dec 1, 2017

I think we should add API to v3 only these parts that are fully compatible with github

@lunny
Copy link
Member Author

lunny commented Dec 1, 2017

@lafriks yes, we can do it easier.

@alexanderadam
Copy link

What if there would be another approach and the functionality of Octotree would directly integrated into gitea?

@alexanderadam alexanderadam mentioned this issue Oct 25, 2019
Closed
@mrsdizzie
Copy link
Member

Closing since upstream Octotree has said they can't support Gitea.

@zeripath zeripath added type/upstream This is an issue in one of Gitea's dependencies and should be reported there status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR labels Sep 7, 2020
@lunny
Copy link
Member Author

lunny commented Sep 9, 2020

Git master announced supported Gitea https://chrome.google.com/webstore/detail/git-master/klmeolbcejnhefkapdchfhlhhjgobhmo

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. type/upstream This is an issue in one of Gitea's dependencies and should be reported there
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@lunny @lafriks @alexanderadam @mrsdizzie @zeripath @sapk