Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

standardize and add instructions to README for publishing the gem #9

Open
olliebun opened this issue Mar 24, 2020 · 1 comment
Open

standardize and add instructions to README for publishing the gem #9

olliebun opened this issue Mar 24, 2020 · 1 comment

Comments

@olliebun
Copy link
Contributor

No description provided.

@olliebun olliebun self-assigned this Apr 8, 2020
@olliebun olliebun removed their assignment Apr 28, 2020
@olliebun
Copy link
Contributor Author

Let's backlog this til we need to do a release.

@olliebun olliebun reopened this May 13, 2020
ZimbiX added a commit that referenced this issue Sep 15, 2022
@ZimbiX
Fix determining gem version from latest git tag
311a664 
It was showing an error:

```
fatal: no tag exactly matches '3467704e40171157184da6f237196c9f4c1b494d'
```

and the version of the gem in the `Gemfile.lock` was being adjusted to 0!

This is different from all (?) of our other gems, which have a version constant defined in a Ruby file. Fixing this was easier than reworking it. I take it this issue is for changing this: #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@olliebun