tvdias / github-tagger Goto Github PK

View Code? Open in Web Editor NEW

33.0 33.0 21.0 909 KB

Github action to tag commit with a given version

License: MIT License

TypeScript 26.06% JavaScript 73.94%

github-tagger's People

Contributors

Stargazers

Watchers

github-tagger's Issues

does not work

Run tvdias/github-tagger@2949d204e2f571a709c2af13a90759460fb56595
6
internal/modules/cjs/loader.js:800
7
    throw err;
8
    ^
9

10
Error: Cannot find module '@actions/core'
11
Require stack:
12
- /home/runner/work/_actions/tvdias/github-tagger/2949d204e2f571a709c2af13a90759460fb56595/lib/main.js
13
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
14
    at Function.Module._load (internal/modules/cjs/loader.js:690:27)
15
    at Module.require (internal/modules/cjs/loader.js:852:19)
16
    at require (internal/modules/cjs/helpers.js:74:18)
17
    at Object.<anonymous> (/home/runner/work/_actions/tvdias/github-tagger/2949d204e2f571a709c2af13a90759460fb56595/lib/main.js:19:27)
18
    at Module._compile (internal/modules/cjs/loader.js:959:30)
19
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
20
    at Module.load (internal/modules/cjs/loader.js:815:32)
21
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
22
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10) {
23
  code: 'MODULE_NOT_FOUND',
24
  requireStack: [
25
    '/home/runner/work/_actions/tvdias/github-tagger/2949d204e2f571a709c2af13a90759460fb56595/lib/main.js'
26
  ]
27
}

Force argument?

It would be good if you could allow a force argument to be passed through to the git call. This will allow existing tags to be re-used.

At the moment if you try to use a tag that already exists you get this error:

Creating tag in another repository

Can this be used for creating tags in another repository within Organization. ?
I didn't find that feature.

Add possibility to skip creating duplicate tag

Hi,

It would be great to add an option of skipping tag creation if the same already exists.
It could help in situations when using automatic semantic versioning and only minor change occurs (e.g. in readme), so the app version doesn't really change, thus instead of failing the job, the step would just finish successfully skipping duplicate tag creation.

Thank you.

Upgrade node version to node16

GitHub has deprecated support for node12 in actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

To continue using this action after Summer 2023 the version of node must be updated.

I would open a PR to do this but I'm not sure how to test the action. Would appreciate any guidance to help with that.