diff options
| author | Patrick Steinhardt <psteinhardt@gitlab.com> | 2023-10-11 14:15:33 +0300 |
|---|---|---|
| committer | Patrick Steinhardt <psteinhardt@gitlab.com> | 2023-10-16 09:45:13 +0300 |
| commit | 9ae33aeb3be039d4ff86323f2dc0aaf389b8a065 (patch) | |
| tree | cc91faa7d458191824ec3daf88001ffaf84ffc93 | |
| parent | 6a2a7cf22046ca29e17bcaed629e997df6901bc2 (diff) | |
protogem: Add URLs to the homepage, source code and bug tracker
Even though we don't link to the location where the source code of our
Ruby Gem exists, rubygems.org does have that information set. It points
to the legacy location of our Ruby Gem though, which is hosted in the
gitlab-org/gitaly-proto repository. It's been ages since we have
deprecated that repository though, so it's kind of puzzling that the
site still has that information. My best guess is that it simply uses
information that was at one point in time present in our Gemspec.
Let's explicitly document these URIs as part of our metadata. As
documented in the specification [1], these URIs should indeed end up on
rubygems.org and thus fix the out-of-date links.
[1]: https://guides.rubygems.org/specification-reference/#metadata
| -rwxr-xr-x | tools/protogem/build-proto-gem | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/tools/protogem/build-proto-gem b/tools/protogem/build-proto-gem index 57c877894..aca451170 100755 --- a/tools/protogem/build-proto-gem +++ b/tools/protogem/build-proto-gem @@ -95,6 +95,12 @@ def build_gem(output_dir, output_path) spec.homepage = "https://gitlab.com/gitlab-org/gitaly" spec.license = "MIT" + spec.metadata = { + "homepage_uri" => "https://gitlab.com/gitlab-org/gitaly", + "bug_tracker_uri" => "https://gitlab.com/gitlab-org/gitaly/-/issues", + "source_code_uri" => "https://gitlab.com/gitlab-org/gitaly/-/tree/master/proto", + } + spec.files = Dir['**/*.rb'] spec.require_paths = [prefix] |