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

Introduce this project to other people #2

Open
motet-a opened this issue Sep 17, 2017 · 4 comments
Open

Introduce this project to other people #2

motet-a opened this issue Sep 17, 2017 · 4 comments
Assignees

Comments

@motet-a
Copy link
Owner

motet-a commented Sep 17, 2017

Explain why this project could be useful, what could be done to improve it, and ask for feedback, suggestions, and help.

@motet-a motet-a self-assigned this Sep 17, 2017
@eggers
Copy link

eggers commented Nov 27, 2017

This is a very cool project, it's something that I've thought about doing myself in a slightly different manner. How hard would it be to generalize it to show a matrix of conflicts between branches rather than pull requests? Something to abstract it from github since we don't use github for source control at my workplace.

@motet-a
Copy link
Owner Author

motet-a commented Nov 28, 2017

Hello,

In fact, you can list long-lived feature branches in the configuration file.
They will be compared just like PRs. Of course, if you often create and remove
feature branches and want to compare them, you’ll often have to edit this
configuration file often so it might be a hassle.

Currently, adding and removing branches through the web interface is
not possible (the whole web interface is entirely read-only), and this feature
may be rather difficult to implement since it may require users
accounts, a sign-up system, a database, etc.

So even if it already kinda works with branches it really depends on your
workflow. Do you want to manage branches manually from the web interface?
Do you want merge-matrix to automatically track the branches? I would like
to learn more about your expectations 🙂

In anyway, supporting other hosting services than GitHub should be pretty easy
since the GitHub API is only used to fetch the repository clone URL and to poll PR
data (name, number, commit hash) every 5 minutes.

@eggers
Copy link

eggers commented Dec 1, 2017

Automatically tracking branches would be great, but if you got it working for gitlab (including private instance), then I'd be very happy.

@motet-a
Copy link
Owner Author

motet-a commented Dec 2, 2017

Thank you for your feedback!

By the way, since this quick-and-dirty prototype is definitely useful for @zestedesavoir but it has various problems due to bad design and can’t handle very well repositories as big as zestedesavoir/zds-site, I consider rewriting it from scratch, possibly in Elixir. This is not a language as ubiquitous as JavaScript but I think it’s really suitable for this kind of long-running applications. I’m open to suggestions 🙂

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

No branches or pull requests

2 participants