Commit Together by Github VS Strict Workflow

• 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.

• Productivity Enhancement
  Strict Workflow helps improve productivity by enforcing the Pomodoro Technique, which involves working in focused bursts with scheduled breaks.
• Distraction Blocking
  The extension automatically blocks distracting websites during work sessions, helping users stay focused on their tasks without getting sidetracked.
• Easy to Use
  With a simple interface, Strict Workflow is easy to set up and use, requiring minimal configuration to get started with a structured workflow.
• Customizable Settings
  Users can customize work and break durations as well as add or remove websites from the block list, tailoring the tool to their specific needs.

Possible disadvantages

• Limited Browser Support
  Strict Workflow is primarily designed for Chrome, which means users of other browsers might not be able to utilize the extension.
• Inflexible Break Enforcement
  The extension enforces breaks strictly according to the timer, which can be a drawback for users who might need to work longer stretches or take unscheduled breaks.
• Potential Over-reliance
  Users might become dependent on the extension to maintain productivity, potentially struggling to focus without it.
• Basic Features
  While effective, the extension offers relatively basic features compared to other productivity tools that might offer additional insights or functionalities.

No Commit Together by Github videos yet. You could help us improve this page by suggesting one.

Strict Workflow Demo

More videos

• 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

• To Software folks here - how do you take care of your health (eyes and back especially)? Long work hours in a software role is straining my eyes and hurting my back due to sitting in front of the screen for that long. How do you all manage?

  As a reminder for taking breaks at regular intervals. I use this chrome extension https://chrome.google.com/webstore/detail/strict-workflow/cgmnfnmlficgeijcalkgnnkigkefkbhd . Set it up based on your requirement. You can also go for a... Source: over 4 years ago