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

[Feature] GitLab repository tracking #112

Open
1 task done
Darylgolden opened this issue Apr 14, 2024 · 3 comments
Open
1 task done

[Feature] GitLab repository tracking #112

Darylgolden opened this issue Apr 14, 2024 · 3 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Darylgolden
Copy link
Contributor

Darylgolden commented Apr 14, 2024

Description

The project could track the number of repositories on GitLab that use creative commons licenses. Similar to

Implementation

  • I would be interested in implementing this feature.
@Darylgolden Darylgolden added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Apr 14, 2024
@Paulooh007
Copy link
Contributor

Paulooh007 commented Apr 14, 2024

I'm really curious how you want to go about this. Given that, unlike GitHub, I don't think GitLab provides a direct way to search for repositories by license through its API. This requires a more manual approach if you're looking to identify licenses across multiple projects.

@TimidRobot

This comment was marked as outdated.

@TimidRobot TimidRobot added help wanted Open to participation from the community 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Apr 15, 2024
@TimidRobot TimidRobot added the 🧹 status: ticket work required Needs more details before it can be worked on label Apr 16, 2024
@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work and removed 🏁 status: ready for work Ready for work 🧹 status: ticket work required Needs more details before it can be worked on labels Jun 20, 2024
@TimidRobot TimidRobot moved this to Backlog in TimidRobot Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

4 participants
@TimidRobot @Darylgolden @Paulooh007 and others