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.

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

Migrated previous GitLab CI code to a GitLab CI/CD Component #486

Open
DarwinJS opened this issue Jul 6, 2024 · 1 comment
Open

Migrated previous GitLab CI code to a GitLab CI/CD Component #486

DarwinJS opened this issue Jul 6, 2024 · 1 comment

Comments

@DarwinJS
Copy link

DarwinJS commented Jul 6, 2024

Describe the bug
@boyter - we've previously collaborated and you have some links to my GitLab CI Include for using this with GitLab.

We had some interest at a GitLab customer in your counter - so I took the previous include code and ported it to a GitLab CI/CD Component - which are reusable, GitLab CI/CD dependencies with version pegging and many other feature.

By default the component will count the current project after using a highly efficient Git Clone. However, it retains the ability to count a set of named projects or a Gitlab Group Heirarchy.

I also found a repository that tries to have examples for every known programming language.

You can find the component here: https://gitlab.com/explore/catalog/guided-explorations/ci-components/scc-code-counter
The source here: https://gitlab.com/guided-explorations/ci-components/scc-code-counter
And the working example here: https://gitlab.com/guided-explorations/ci-components/working-code-examples/sample-programs
Here's an example job log from the working example: https://gitlab.com/guided-explorations/ci-components/working-code-examples/sample-programs/-/jobs/7278841658

To Reproduce

  1. Tell us how you were using scc either as command line or library.
  2. If command line please list the arguments. If library please supply code to demonstrate the issue.
  3. If the issue is a miscount or some such please link or supply a file which demonstrates the issue.

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

  • OS: [e.g. macOS, Windows, Linux]
  • Version [e.g. 22]
@boyter
Copy link
Owner

boyter commented Jul 21, 2024

Great. So not sure what you want me to do here? Update the README.md to point at the new links and such?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants