Review options and mark some as deprecated due to `orgs` and `users` introduction at API level

[mborne]

Options

Client parameters for hosted GIT API

Name	Description	Example
gitlab-url	URL of git hosting service	http://gitlab.localhost
gitlab-token	Auth token for git hosting API

This parameters should be renamed to url and token (it has no effect for users as it they are not options but command line arguments.

Filter projects

Name	Description	Example
--orgs	Filter projects according to orgs/groups	symfony,FriendsOfSymfony
--users	Filter projects according to users	mborne,ochorocho
--include-if-has-file	Filter projects that doesn't contains a given file	.satisinclude
--project-type	Filter projects according to type defined in composer.json	library
--ignore	Filter projects according to a regexp	(^phpstorm)
--projectFilter	DEPRECATED Filter projects using search parameter in GITLAB API
--gitlab-namespace	DEPRECATED Filter projects according to gitlab-namespace	2,Diaspora

SATIS generation

Name	Description	Example
--template	Use a custom SATIS template instead of default one	satis-template.json
--name	Define SATIS repository name	mborne/satis-gitlab-repository
--homepage	Define SATIS URL appearing in HTML web page	http://satis.localhost
--archive	Download tar ball for dependencies (mirror mode)
--no-token	Disable gitlab-token saving in generated satis.json
--output	Remplace default output path for satis.json

Deprecated options

--projectFilter

This option has been introduced to have the hability to filter gitlab.com projects
while listing projects at API level.

--orgs and --users will provide a better control for this use case. --ignore, --include-if-has-file and co will provide a stronger control to complete the job.

--gitlab-namespace

The current implementation is not based on the API of the git hosting service.

--orgs option is more efficient as it provides gitlab group filtering at API level and makes it faster to filter by group on gitlab.com for example.

[MaximeCulea]

Hi @mborne, could you tell me how to use the --projectFilter for more than the first 20 per page projects? I would do something like gitlab.com/api/v4/projects?private_token=xx&per_page=100
This is because Gitlab now use restrictions on API.
Many thanks

[mborne]

Hi @MaximeCulea ,

Sorry for response time (haven't seen the notif). Currently, there is no option for that ( see https://github.com/mborne/remote-git/blob/923688c03636b38091206980b2562b919b1aaa18/src/Gitlab/GitlabClient.php#L29-L30 )

I might change the default value or add GITLAB_PER_PAGE env variable. Please create an issue on https://github.com/mborne/remote-git.