cosydney

True that, I've made a quick loom so you can check it out: https://www.loom.com/share/42a7b62cbbf24eb39d7eac0a57ffb5f8

Most importantly we don't require to share the code from gitbhub. Github: Reads permissions repository, issues, teams, pull requests. Write: Pull Requests (so that we can write the conversations that happen in slack) Slack: read and write Members, channels and private message to the bot

What do you mean exactly? If someone else reviews unstead of the person who has been asked ?

Thanks. We are rolling out more settings to make it customizable for each teams.

2. Nothing stops them, we plan on moving fast listening to our users. For now bigger companies are asking for specifics analytics

Habits are hard to break !

Right, I think Axolo makes it possible for your reviewer to respond quickly to something he sees and also makes it easy to be the next priority for your reviewer.

Hey, happy to discuss we might be hiring soon ! shoot us an email on hey @ getchaos.app

It can be automatically archived, and all of the conversations is being posted into github to keep the documentation.

Yes it makes sense, especially since Microsoft also owns Github ! will give it more thought thank you.

We've also encountered that problem in some cases. Stacked PR are difficult to manage. We could potentially have multiple PR into a single channel to make communication easier abroad stacked PR.

To this date we don't have access to the code and it's easier for companies to try us this way. So not sure we will go too much into details on this topic.

Stacked PR shouldn't exist, or at least rarely. We plan to introduce analytics and we think that too many stacked PR should be a warning that something is not right.

Thank you for sharing mattermost, didn't know that. it's interesting to see Pull Requests as an 'incident' that needs to be resolved by different party. It didn't made sense to make Axolo Open source at the beginning but we are considering it today.

Agreed. I pursue the idea that we should be able to talk in an easy way about the code we produce.

We bumped on Codestream with one of the person who works at Axolo, we had this idea in mind but after talking to many developers we realized that no one mentionned creating PR with their IDE or having direct conversations from there. We want Axolo to fit in well in developers habits => Using slack for messaging and code editors to code.

Yes, one should only receive relevant notifications.

Hey, We made this tool for front end developers who want a quick and easy way to create an API that will be as close as possible to something in production.

We've seen people using it for tutorials, teaching and more ! Curious to see if this would be useful for you.

In your opinion is Amazon one of those company that deviates from their core DNA ? Or is their DNA one that strive for novelty and adaptability to constant change (Novelty in business models and constantly challenging themself to find new ways of making money) ?