Alessandro Pinna

We did it! https://github.com/sorintlab/stolon/pull/817 Is it enough clear the message of warning? Should we add a log of warning? Thanks

> @sgotti the usefulness is to have a current global view of the agola status, because for example it happens that your run remains in the queue for a long...

> * What about user repositories, private org repositories etc? The intention would be to also display the runs about user repositories, private org repositories, directruns.

We can use a Cursor with this data ``` StartID string PointsNext bool OrderBy string SortOrder SortOrder Filters map[string]string Limit int ``` `StartID `contain the starting data id(excluded) to fetch...

I remove PointsNext since we maintain only one cursor for the next page, so the cursor contains this data: ``` StartID string OrderBy string SortOrder SortOrder Filters map[string]string Limit int...

> > Filters map[string]string > > Don't be rigid on this. Filters, but also the other fields could be different based on the api. @sgotti I can define the Cursor...

@sgotti when the user call the last page do you think is better to return an empty cursor(so it know there are no other pages to ask) or the cursor...

@sgotti with the APIs list secrets/variables I think the pagination can not work when the client use the `removeoverridden` parameter, because this filter is implemented by the gateway. For example...

> * I tried to create a projectgroup under my user via cli > > ``` > agola projectgroup create -n PGNAME --parent user/USERNAME --token TOKEN > > 2023-12-12T21:53:59.488231024Z INF...

@grapemix I need to see the log of the failed run to understand better. I can see you are setting the AGOLA_SKIPSSHHOSTKEYCHECK variable; but it is passed automatically by the...