Collect website feedback from your team, clients, and users.
Get feedback with screenshots & technical metadata directly into your favorite project management tool.
Say goodbye to messy emails, spreadsheets and powerpoint. There is a better way!
Based on our record, Pijul should be more popular than Marker.io. It has been mentiond 44 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Using theory of patches would better compliment the current approach. Integrating a scm such as https://pijul.org or atleast the underlying tech would allow for better conflict resolutions. Transferring patches should also allow for more efficient use of io. - Source: Hacker News / 5 days ago
IMO Open Source software communities are where folks like you can really thrive. They're much closer at something like a meritocracy than traditional workplaces. > I want to make the next-gen version control system While you certainly could invent one yourself, you could consider contributing to popular ones like git/mercurial. It'd help teach you both the positive and the negative aspects of their design... - Source: Hacker News / 21 days ago
The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking "Does $branch contain $patch" basically impossible to answer. https://pijul.org/ greatly improves this... - Source: Hacker News / about 1 month ago
In Pijul, conflicts are not modelled as a "failure to merge", but rather as the standard case. Specifically, conflicts happen between two changes, and are solved by one change. The resolution change solves the conflict between the same two changes, no matter if other changes have been made concurrently. Once solved, conflicts never come back. - from https://pijul.org/. - Source: Hacker News / 4 months ago
Do not try and bend the spoon, that's impossible. Instead, only try to realize the truth...there is no spoon. Then you will see it is not the spoon that bends, it is only yourself -- what Pijul users say when they overhear git users arguing with each other about monorepos. https://pijul.org/. - Source: Hacker News / 4 months ago
This is a really nice note and solution of the problem. What is the difference from your competitor https://marker.io/? - Source: Hacker News / over 1 year ago
I'm looking for a free and/or open source self-hosted alternative to marker.io for visual bug tracking/reporting. Source: over 1 year ago
Also keep an eye on this discussion to make issue forms available on private repos. Until this is possible, marker.io & Linear are a solution. Source: about 2 years ago
I work for a really small startup ( https://marker.io ) that focuses on drastically improving website feedback workflows for agencies/ clients. In some cases agencies say:. Source: about 2 years ago
Obviously I'm biased and a bit self-promotional but we put so much work into it, that I'd love to get your feedback -> https://marker.io. Source: almost 3 years ago
Mercurial SCM - Mercurial is a free, distributed source control management tool.
BugHerd - BugHerd: The Website Feedback Tool for Agencies
Git - Git is a free and open source version control system designed to handle everything from small to very large projects with speed and efficiency. It is easy to learn and lightweight with lighting fast performance that outclasses competitors.
Usersnap - Usersnap is a customer feedback software for SaaS companies that need to constantly improve and grow their products.
GitHub Desktop - GitHub Desktop is a seamless way to contribute to projects on GitHub and GitHub Enterprise.
Userback - Visual. Feedback. Fast. See any web page through your customers eyes with video screen capture and annotated screenshots.