resolve-or-create the release by tag to avoid the 409 'Release is has no Tag'
when a release already exists for the tag (e.g. one made manually in the UI)
use POST /releases/{id}/assets with multipart field 'attachment'
(was the obsolete /_attachments route with field 'file')
- resolve-or-create the release by tag to avoid the 409 'Release is has no Tag'
when a release already exists for the tag (e.g. one made manually in the UI)
- use POST /releases/{id}/assets with multipart field 'attachment'
(was the obsolete /_attachments route with field 'file')
- resolve-or-create the release by tag to avoid the 409 'Release is has no Tag'
when a release already exists for the tag (e.g. one made manually in the UI)
- use POST /releases/{id}/assets with multipart field 'attachment'
(was the obsolete /_attachments route with field 'file')
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
robot
when a release already exists for the tag (e.g. one made manually in the UI)
(was the obsolete /_attachments route with field 'file')
- resolve-or-create the release by tag to avoid the 409 'Release is has no Tag' when a release already exists for the tag (e.g. one made manually in the UI) - use POST /releases/{id}/assets with multipart field 'attachment' (was the obsolete /_attachments route with field 'file')c2659dcb1dtode9d537a75