I want to share my wakatime goals into GitHub README.
I tried to find other GitHub profile that share their templates, but i did not find any goal stats.
Do I need to create myself if there isn't any?
And how?
You can check out athul/waka-readme
Dev Metrics in Readme
You might need to fork that repository, and modify main.py in order to add Goals:
listing your goals: GET /api/v1/users/:user/goals
reading a goal: GET /api/v1/users/:user/goals/:goal
Related
I am looking into improving the workflow my colleague and myself are using for BitBucket. Something that is often forgotten is the documentation for the feature we are working on therefore I thought I good way to 'don't forget' would be to add a Task as soon as a Pull request is created for a particular branch.
The first think a developer should do after creating the Pull Request would be:
- Add a comment, something like WIP (Work in Progress)
- Create a task underneath, something like 'Add documentation'
In this way, we won't be able to 'Merge' the branch into 'Develop' if All tasks are not completed (this is how it is currenly configured).
Rather than having the developer to do so, it would be good if we can have the system to do so as soon as we create the Pull Request.
Is that possible?
I had searchd on Internet, to be honest I didn't understand if taht functionality comes with like the Premium package or if it is an Add-On...who knows.
Thanks :)
Atlassian recently added a 'Default Pull Request Tasks' feature to Bitbucket Cloud.
The same functionality was previously available as a Bitbucket app, but it was removed in May 2020. It's now a native feature.
Product announcement: https://bitbucket.org/blog/bitbucket-cloud-product-updates-august-2022
Feature details: https://bitbucket.org/blog/default-pull-request-tasks
You can try this. It is free for 30 days.
https://marketplace.atlassian.com/apps/1225598/default-tasks-for-pull-requests?tab=pricing&hosting=datacenter
I did not find any free solutions.
i was trying to get the list of projects in my gitlab using Git api. for that i was following Git lab api instruction.
they said i can access the list of project by this link:
https://gitlab.com/api/v4/projects?access_token=some_token.
but unfortunately with the above link i got bunch of information, which is not mine at all. i got the information which is owned by other users.
In that case how am i able the get my own projects information?
Nevertheless, the respond JSON has so many attribute. is there anyway that i can achieve the attribute according to my desire?
You can use owned=true to get only project which you are owner and simple=true to have limited field, check this :
https://gitlab.com/api/v4/projects?access_token=some_token&owned=true&simple=true
Is it possible to to filter the gitlab project api by date. An example of this would be to identified all the projects that were modified last week.
I reviewed the documentation but could not see this called out. https://gitlab.com/help/api/projects.md
Does anyone have an idea of a way to accomplish this other than file tracking?
From the document you linked, it looks like you can Get /projects and then add the attribute order_by. So you can add something like:
GET /projects?order_by=last_activity_at
I am using GitLab 6.9.2 e46b644, I can not find any API to rename a group from API doc, but from gitlab UI, it really support rename group.
any idea if I need to batch rename groups?
Thanks in advance.
As you've said, it's not documented at: https://github.com/gitlabhq/gitlabhq/blob/4a5044e30269f8b3c6c075093cd4646a478231c7/doc/api/groups.md
Also, it's not implemented at: https://github.com/gitlabhq/gitlabhq/blob/4a5044e30269f8b3c6c075093cd4646a478231c7/lib/api/groups.rb which would be the obvious place.
And I could not find any feature request at http://feedback.gitlab.com
So I think it is safe to assume that it is not possible. I recommend that you open a feature request at http://feedback.gitlab.com
I created new asserts in the package KernelTests-Numbers of squeak. I cannot find a way to check out these to Squeaksource (a repo) or with monticello. How to check out new tests into the repository http://source.squeak.org/trunk to spread it to the community?
Thanks for the answers in advance.
EDIT
Thanks Tobias.
Here is the Monticello-Code for the Inbox:
MCHttpRepository
location: 'http://source.squeak.org/inbox'
user: ''
password: ''
EDIT 2
Thanks Bert for the Step-by-Step-Manual and screencast link.
Regards,
bartak
The steps are basically
Update so you have the latest trunk versions
Check the package changes against Trunk repo
Make sure only the methods you actually touched are listed
Save your package to the Inbox repo, giving it a reasonable commit message
Here is a video I made about how to submit a new package. Note this is for Etoys, so whenever I talk about the "etoys" repo you need to use "trunk", and instead of "etoys-inbox" you use "inbox". The relevant part is from about 1:20 to 4:00 min:
https://www.youtube.com/watch?v=2QKmfI4taGo#t=1m20s
You put into another repository, called the inbox:
http://source.squeak.org/inbox
From there, Squeak core developers can merge into the trunk repository.
The whole process is described in A New Community Development Model.
You probably want to talk about your changes on squeak-dev.