diff-lcs 1.6.2 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 34fc249139fb5ed40b525cf33d8e4e3d3702384f74d1e67e63d8eed54a09133c
-  data.tar.gz: 46739e6b242db46dd6d01c4bb26d7c51fc07ccaebd7ecd58c305d758f30dfc33
+  metadata.gz: b8edc3b3383f33e30269bdef56fd21d58ac8efe471bb202f129d659a4f1a5ead
+  data.tar.gz: 681426cabb34022d55a8335b4dcf095dc5b97faeddc4bbe82793a2cba36c6729
 SHA512:
-  metadata.gz: c482d6b11cb38b840ee4a4c11785c592a7a537e5f855cca99739a578e8d833b05ad43cba4ac8e40e4ae1fa876633d9d96c18c29acef63bf72532c352d98b05e6
-  data.tar.gz: 7c6da2681b6a2ddf4ebda85deb24aeaeea29218cfa452d40717e1963c117c95230da2c01c18b806cb0916a804263aa7ac0230c4adcbb8fb1b30a95faee5a4dda
+  metadata.gz: db895eb27c2215803f6da307375044c456fe7a09250d86d3be8fd176e22cc6aef71d3767fd6901c62c3a9a5c1035e282570a535fe365bff8af9ce1459d937687
+  data.tar.gz: 948fd71bb838124c75c594921a5225358785b40d36d4b3bae60bd0d17914f1b3aa9ab71715e25c488028a67fb660a41808036ffa955b3802505dc9dce83d13fc

data/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Changelog
 
+## 2.0.0 / 2026-02-01
+
+This release has significant **breaking changes**.
+
+- diff-lcs 2 supports Ruby 3.2 or higher. This allowed:
+
+  - readability improvements (endless methods, pattern matching);
+
+  - support for immutable Data classes (`Diff::LCS::Block`, `Diff::LCS::Change`,
+    and `Diff::LCS::ContextChange`);
+
+  - removal of compatibility shims;
+
+  - reduction in conditional tests in loops, especially for String character
+    extraction (compare `string ? seq[i, 1] : seq[i]` to `seq[i]`); and
+
+  - optimizations to string and relying on standard encoding support present
+    since Ruby 2.1.
+
+  The primary API (methods and class methods on `Diff::LCS`) has not changed,
+  with one exception noted below. Internal APIs (including `Diff::LCS::Block`,
+  `Diff::LCS::Change`, `Diff::LCS::ContextChange`, and `Diff::LCS::Hunk`) have
+  changed for compatibility.
+
+- The `htmldiff` binary and supporting code have been removed without
+  replacement.
+
+- `ldiff` no longer supports `ed`-script output (`ed` and `reverse_ed` formats).
+  As Baptiste Courtois says in [#108][pull-108], the "implementation was broken
+  for a while and no-one reported it."
+
+- The method `Diff::LCS.LCS` has been removed as an alias for `Diff::LCS.lcs`.
+  Most callers are using `Diff::LCS.lcs` and modern Ruby did-you-mean support
+  should assist with this update.
+
+- `Diff::LCS::Change` objects implemented the comparison operator (`<=>`)
+  incorrectly. Comparisons are now done so that the `position` is compared
+  first, then the `action` (by index of `VALID_ACTIONS`), and finally the
+  element. `Diff::LCS::ContextChange` works similarly, comparing the old and new
+  positions prior to comparing the actions by index.
+
+  The order of `VALID_ACTIONS` was changed for the index order to make sense.
+
+- `ldiff` now implements `-` as a filename option for standard input. This is
+  used for integration testing with RSpec like this:
+
+  ```console
+  rspec -Ilib -rdiff/lcs integration/failure/array_diff_spec.rb 2>&1 |
+    ruby -Ilib bin/ldiff -U integration/golden/array_diff.txt -
+  ```
+
+- diff-lcs no longer uses RSpec as its test suite, but instead uses Minitest.
+  The conversion to Minitest and the new RSpec integration tests
+  (`rake integration`) were written with the assistance of [Kiro][kiro] and
+  verified manually, with portions changed as required.
+
+- The code of conduct was updated to the Contributor Covenant 3.0.
+
 ## 1.6.2 / 2025-05-12
 
 - Handle upcoming changes to the `cgi` gem in Ruby 3.5 ([#147][pull-147])
@@ -25,8 +83,9 @@
 
 ## 1.6.0 / 2025-02-13
 
-- Baptiste Courtois (@annih) has done significant work on making `bin/ldiff`
-  work better, contributing a number of issues and pull requests. These include:
+- Baptiste Courtois ([@annih][gh-user-annih]) has done significant work on
+  making `bin/ldiff` work better, contributing a number of issues and pull
+  requests. These include:
 
   - Separation of command parsing from diff-generation in `Diff::LCS::Ldiff`
     code extraction making it easier to use separately from the `bin/ldiff`
@@ -385,8 +444,8 @@
 
 ## 1.1.1 / 2004-09-25
 
-- Fixed bug #891 (Set returned from patch command does not contain last equal
-  part).
+- Fixed bug [#891][gh-issue-891] (Set returned from patch command does not
+  contain last equal part).
 
 - Fixed a problem with callback initialisation code (it assumed that all
   callbacks passed as classes can be initialised; now, it rescues NoMethodError
@@ -504,6 +563,7 @@
 [pull-103]: https://github.com/halostatue/diff-lcs/pull/103
 [pull-104]: https://github.com/halostatue/diff-lcs/pull/104
 [pull-105]: https://github.com/halostatue/diff-lcs/pull/105
+[pull-108]: https://github.com/halostatue/diff-lcs/pull/108
 [pull-129]: https://github.com/halostatue/diff-lcs/pull/129
 [pull-147]: https://github.com/halostatue/diff-lcs/pull/147
 [pull-148]: https://github.com/halostatue/diff-lcs/pull/148
@@ -516,3 +576,6 @@
 [standard ruby]: https://github.com/standardrb/standard
 [tidelift]: https://tidelift.com/security
 [tp]: https://guides.rubygems.org/trusted-publishing/
+[kiro]: https://kiro.dev
+[gh-user-annih]: https://github.com/annih
+[gh-issue-891]: https://github.com/halostatue/diff-lcs/issues/891

data/CODE_OF_CONDUCT.md

@@ -1,128 +1,166 @@
-# Contributor Covenant Code of Conduct
+# Contributor Covenant 3.0 Code of Conduct
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status. The
+same privileges of participation are extended to everyone who participates in
+good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of
+   gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our
+   community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this Code of
+Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
+   toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a
+   way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which
+   includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can help
+avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a
+possible violation, create a [private security advisory][advisory] — violations
+of this code of conduct are considered security vulnerabilities.
+
+Community Moderators take reports of violations seriously and will make every
+effort to respond in a timely manner. They will investigate all reports of code
+of conduct violations, reviewing messages, logs, and recordings, or interviewing
+witnesses and other participants. Community Moderators will keep investigation
+and enforcement actions as transparent as possible while prioritizing safety and
+confidentiality. In order to honor these values, enforcement actions are carried
+out in private with the involved parties, but communicating to the whole
+community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct
+has been violated, the following enforcement ladder may be used to determine how
+best to repair harm, based on the incident's impact on the individuals involved
+and the community as a whole. Depending on the severity of a violation, lower
+rungs on the ladder may be skipped.
+
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or interactions
+      with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators have
+      tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3. Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the suspension
+      is lifted.
+
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that the
+      Community Moderators determine there is no way to keep the community safe
+      with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of Community Managers to use their discretion and judgment, in keeping
+with the best interests of our community.
 
 ## Scope
 
 This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
+an individual is officially representing the community in public or other
+spaces. Examples of representing our community include using an official email
+address, posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at [INSERT CONTACT
-METHOD]. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
+permanently available at <https://www.contributor-covenant.org/version/3/0/>.
 
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+<https://creativecommons.org/licenses/by-sa/4.0/>.
 
-For answers to common questions about this code of conduct, see the FAQ at
-<https://www.contributor-covenant.org/faq>. Translations are available at
-<https://www.contributor-covenant.org/translations>.
+For answers to common questions about Contributor Covenant, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are provided at
+<https://www.contributor-covenant.org/translations>. Additional enforcement and
+community guideline resources can be found at
+<https://www.contributor-covenant.org/resources>. The enforcement ladder was
+inspired by the work of [Mozilla’s code of conduct team][inclusion].
 
-[homepage]: https://www.contributor-covenant.org
-[Mozilla CoC]: https://github.com/mozilla/diversity
+[advisory]: https://github.com/halostatue/diff-lcs/security/advisories/new
+[inclusion]: https://github.com/mozilla/inclusion

data/CONTRIBUTING.md

@@ -1,31 +1,36 @@
 # Contributing
 
-Contribution to diff-lcs is encouraged in any form: a bug report, a feature
-request, or code contributions. There are a few DOs and DON'Ts for
-contributions.
+Contribution to diff-lcs is encouraged: bug reports, feature requests, or code
+contributions. New features should be proposed and discussed in an
+[issue][issues].
 
-- DO:
+Before contributing patches, please read the [Licence](./LICENCE.md).
 
-  - Keep the coding style that already exists for any updated Ruby code (support
-    or otherwise). I use [Standard Ruby][standardrb] for linting and formatting.
+diff-lcs is governed under the [Contributor Covenant Code of Conduct][cccoc].
 
-  - Use thoughtfully-named topic branches for contributions. Rebase your commits
-    into logical chunks as necessary.
+## Code Guidelines
 
-  - Use [quality commit messages][qcm].
+I have several guidelines to contributing code through pull requests:
 
-  - Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
-    `CHANGELOG.md` as a separate commit from your main change. (Follow the style
-    in the `CHANGELOG.md` and provide a link to your PR.)
+- All code changes require tests. In most cases, this will be added or updated
+  unit tests. I use [Minitest][minitest].
 
-  - Add or update tests as appropriate for your change. The test suite is
-    written in [RSpec][rspec].
+  - There are integration tests with RSpec which must not be broken, accessible
+    through `rake integration`. This requires a non-bundled RSpec,
+    `gem install rspec`.
 
-  - Add or update documentation as appropriate for your change. The
-    documentation is RDoc; diff-lcs does not use extensions that may be present
-    in alternative documentation generators.
+- I use code formatters, static analysis tools, and linting to ensure consistent
+  styles and formatting. There should be no warning output from test run
+  processes. I use [Standard Ruby][standardrb].
 
-- DO NOT:
+- Proposed changes should be on a thoughtfully-named topic branch and organized
+  into logical commit chunks as appropriate.
+
+- Use [Conventional Commits][conventional] with my
+  [conventions](#commit-conventions).
+
+- Versions must not be updated in pull requests unless otherwise directed. This
+  means that you must not:
 
   - Modify `VERSION` in `lib/diff/lcs/version.rb`. When your patch is accepted
     and a release is made, the version will be updated at that point.
@@ -36,6 +41,30 @@ contributions.
 
   - Modify the `Gemfile`.
 
+- Documentation should be added or updated as appropriate for new or updated
+  functionality. The documentation is RDoc; diff-lcs does not use extensions
+  that may be present in alternative documentation generators.
+
+- All GitHub Actions checks marked as required must pass before a pull request
+  may be accepted and merged.
+
+- Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
+  `CHANGELOG.md` as a separate commit from your main change. (Follow the style
+  in the `CHANGELOG.md` and provide a link to your PR.)
+
+- Include your DCO sign-off in each commit message (see [LICENCE](LICENCE.md)).
+
+## AI Contribution Policy
+
+diff-lcs is a library with complex interactions and subtle decisions (some of
+them possibly even wrong). It is extremely important that contributions of any
+sort be well understood by the submitter and that the developer can attest to
+the [Developer Certificate of Origin][dco] for each pull request (see
+[LICENCE](LICENCE.md)).
+
+Any contribution (bug, feature request, or pull request) that uses undeclared AI
+output will be rejected.
+
 ## Test Dependencies
 
 diff-lcs uses Ryan Davis's [Hoe][Hoe] to manage the release process, and it adds
@@ -44,28 +73,55 @@ tests in the same way that `rake spec` does.
 
 To assist with the installation of the development dependencies for diff-lcs, I
 have provided a Gemfile pointing to the (generated) `diff-lcs.gemspec` file.
-`minitar.gemspec` file. This will permit you to use `bundle install` to install
-the dependencies.
+This will permit you to use `bundle install` to install the dependencies.
 
 You can run tests with code coverage analysis by running `rake spec:coverage`.
 
-## Workflow
+## Commit Conventions
+
+diff-lcs has adopted a variation of the Conventional Commits format for commit
+messages. The following types are permitted:
+
+| Type    | Purpose                                               |
+| ------- | ----------------------------------------------------- |
+| `feat`  | A new feature                                         |
+| `fix`   | A bug fix                                             |
+| `chore` | A code change that is neither a bug fix nor a feature |
+| `docs`  | Documentation updates                                 |
+| `deps`  | Dependency updates, including GitHub Actions.         |
+
+I encourage the use of [Tim Pope's][tpope-qcm] or [Chris Beam's][cbeams]
+guidelines on the writing of commit messages
+
+I require the use of [git][trailers1] [trailers][trailers2] for specific
+additional metadata and strongly encourage it for others. The conditionally
+required metadata trailers are:
+
+- `Breaking-Change`: if the change is a breaking change. **Do not** use the
+  shorthand form (`feat!(scope)`) or `BREAKING CHANGE`.
+
+- `Signed-off-by`: this is required for all developers except me, as outlined in
+  the [Licence](./LICENCE.md#developer-certificate-of-origin).
 
-Here's the most direct way to get your work merged into the project:
+- `Fixes` or `Resolves`: If a change fixes one or more open [issues][issues],
+  that issue must be included in the `Fixes` or `Resolves` trailer. Multiple
+  issues should be listed comma separated in the same trailer:
+  `Fixes: #1, #5, #7`, but _may_ appear in separate trailers. While both `Fixes`
+  and `Resolves` are synonyms, only _one_ should be used in a given commit or
+  pull request.
 
-- Fork the project.
-- Clone your fork (`git clone git://github.com/<username>/diff-lcs.git`).
-- Create a topic branch to contain your change
-  (`git checkout -b my_awesome_feature`).
-- Hack away, add tests. Not necessarily in that order.
-- Make sure everything still passes by running `rake`.
-- If necessary, rebase your commits into logical chunks, without errors.
-- Push the branch up (`git push origin my_awesome_feature`).
-- Create a pull request against halostatue/diff-lcs and describe what your
-  change does and the why you think it should be merged.
+- `Related to`: If a change does not fix an issue, those issue references should
+  be included in this trailer.
 
+[cbeams]: https://cbea.ms/git-commit/
+[cccoc]: ./CODE_OF_CONDUCT.md
+[conventional]: https://www.conventionalcommits.org/en/v1.0.0/
+[dco]: licences/dco.txt
 [hoe]: https://github.com/seattlerb/hoe
-[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-[release-gem]: https://github.com/rubygems/release-gem
-[rspec]: http://rspec.info/documentation/
+[issues]: https://github.com/halostatue/diff-lcs/issues
+[minitest]: https://github.com/seattlerb/minitest
+[rspec]: https://rspec.info/documentation/
 [standardrb]: https://github.com/standardrb/standard
+[tpope-qcm]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[trailers1]: https://git-scm.com/docs/git-interpret-trailers
+[trailers2]: https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---trailerlttokengtltvaluegt

data/CONTRIBUTORS.md

@@ -1,26 +1,26 @@
 # Contributors
 
-- Austin Ziegler (@halostatue) created diff-lcs.
+- Austin Ziegler ([@halostatue][gh-user-halostatue]) created diff-lcs.
 
 Thanks to everyone else who has contributed to diff-lcs over the years:
 
-- @ginriki
-- @joshbronson
-- @kevinmook
-- @mckaz
+- [@ginriki][gh-user-ginriki]
+- [@joshbronson][gh-user-joshbronson]
+- [@kevinmook][gh-user-kevinmook]
+- [@mckaz][gh-user-mckaz]
 - Akinori Musha
 - Artem Ignatyev
 - Brandon Fish
-- Baptiste Courtois (@annih)
+- Baptiste Courtois ([@annih][gh-user-annih])
 - Camille Drapier
 - Cédric Boutillier
-- @earlopain
+- [@earlopain][gh-user-earlopain]
 - Gregg Kellogg
 - Jagdeep Singh
 - Jason Gladish
 - Jon Rowe
 - Josef Strzibny
-- Josep (@apuratepp)
+- Josep ([@apuratepp][gh-user-apuratepp])
 - Josh Bronson
 - Jun Aruga
 - Justin Steele
@@ -44,6 +44,16 @@ Thanks to everyone else who has contributed to diff-lcs over the years:
 - Ryan Lovelett
 - Scott Steele
 - Simon Courtois
-- Tien (@tiendo1011)
+- Tien ([@tiendo1011][gh-user-tiendo1011])
 - Tomas Jura
 - Vít Ondruch
+
+[gh-user-halostatue]: https://github.com/halostatue
+[gh-user-ginriki]: https://github.com/ginriki
+[gh-user-joshbronson]: https://github.com/joshbronson
+[gh-user-kevinmook]: https://github.com/kevinmook
+[gh-user-mckaz]: https://github.com/mckaz
+[gh-user-annih]: https://github.com/annih
+[gh-user-earlopain]: https://github.com/earlopain
+[gh-user-apuratepp]: https://github.com/apuratepp
+[gh-user-tiendo1011]: https://github.com/tiendo1011