search

Estia-1a / projetGenieInfo_public

This is the main repository for the Estia First Year Computer Science Project
MIT License
1 stars 2 forks source link

Question : can we force the issue index #9

Closed dhmmasson closed 2 years ago

dhmmasson commented 2 years ago

so that we know which issues is what ? Maybe if we create the issue through the API

dhmmasson commented 2 years ago

Create an issue

Any user with pull access to a repository can create an issue. If issues are disabled in the repository, the API returns a 410 Gone status.

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See "Secondary rate limits" and "Dealing with secondary rate limits" for details.

octokit.rest.issues.create({
  owner,
  repo,
  title,
});

Parameters

name | required | description -- | -- | -- owner | yes |   repo | yes |   title | yes | The title of the issue. body | no | The contents of the issue. assignee | no | Login for the user that this issue should be assigned to. NOTE: Only users with push access can set the assignee for new issues. The assignee is silently dropped otherwise. This field is deprecated. milestone | no |   labels | no | Labels to associate with this issue. NOTE: Only users with push access can set labels for new issues. Labels are silently dropped otherwise. assignees | no | Logins for Users to assign to this issue. NOTE: Only users with push access can set assignees for new issues. Assignees are silently dropped otherwise.

See also: GitHub Developer Guide documentation.

dhmmasson commented 2 years ago

So Apparently, not exactly.

But reading :

Creating content too quickly using this endpoint may result in secondary rate limiting. Remind me that in Prog Avancée, creating the issue would sometime failed du to secondary rate limiting... I'd say you should have a very slow, and deliberate creation of the issues to prevent that. (i.e. create the first issue, wait, create the second, wait.. )

WilliamDelamare commented 2 years ago

Not sure I understand what the issue is about: index (and what do you mean by that?) or the notification/timeout problem? For the timeout, yeah, we can easily add a 1s delay between issue creation (or more, I should check the doc). For the index, more details are needed ^^