This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

This task has been migrated to GitLab.

Sure go ahead ;)

Hey @faux, I am still working on this.

Hey, I was wondering if @nahimilega is still working on this? If not then can I poke into this as it would be a good practice for me before implementing launchpad lister and gogs lister. Thanks :)

In T808#30140, @nahimilega wrote:

Now the problem is base url and the api token for each phabricator is different so I am not able to understand how to deal with this?
Can anyone please help me?

Respected all,
I am now to this community and this is my first task.Can you please mentor me in solving this?

Sure, just go ahead: there is no need to "reserve" tasks as a prerequisite to work on them. Just submit a diff against the lister repo as a diff when you've something ready to review :-)

Resected all,
I would love to complete this task. And it would be a good starting point for me for implementing new listers.

with your proposal, implementation, and documentation updated, this can be closed.

Thanks by the way!

I've documented the extra hoops people need to jump through for git push to work on https://wiki.softwareheritage.org/index.php?title=Code_review_in_Phabricator&type=revision&diff=964&oldid=899

I've moved the repositories that need it to have their staging area set to https.

In T1522#27987, @ardumont wrote:

use https for the staging area configuration (which will allow people to push it even if nothing is configured, by just typing their password)

That'd mean also to change that uri to be read/write, it's read-only for now.

use https for the staging area configuration (which will allow people to push it even if nothing is configured, by just typing their password)

sounds like a plan!

One more possibility is to document that people need to setup an ssh key on their account to be able to push their changes.