SubmitMap VS Commit Together by Github

• Possible time savings
  I can't verify what SubmitMap offers. If it works as a submission or directory-listing tool, as the name suggests, it could save time by letting you submit a site or project to many places from one spot instead of doing it manually.
• Potential visibility boost
  Services in this category usually aim to increase exposure, backlinks, and discovery. If the listings are real, they could bring some referral traffic and help with early-stage awareness.
• Centralized workflow
  A single place to manage submissions or listings can make it easier to track where your project has been submitted and avoid duplicates.
• Useful for early-stage launches
  Founders and indie makers with little marketing budget might find a tool like this a cheap way to get their first listings and initial exposure.
• Simple concept
  The name implies a narrow, focused purpose, which typically means a short learning curve and less setup than a full marketing suite.

Possible disadvantages

• Unverified features and claims
  I have no reliable information about SubmitMap's features, pricing, or track record. Check the site directly and read independent reviews before committing time or money.
• Uncertain SEO value
  Many directory and submission services give low-quality or nofollow links that bring little ranking benefit. Mass submissions can sometimes look spammy to search engines.
• Limited traffic quality
  Visitors from directory-style listings are often casual browsers rather than engaged users, so conversion rates may be low.
• Possible cost versus return
  If the service is paid or has premium tiers, the return on investment may be unclear compared with content marketing, social media, or targeted outreach.
• Limited reputation and support information
  A newer or lesser-known platform may have few public reviews, community feedback, or documented support channels, which makes it harder to judge reliability.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

Tracking SubmitMap since Aug 2026.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago