httpoison VS tokens

You can also use https://github.com/edgurgel/httpoison to write your own API integrations. If there's already a package out there, may as well use it. If not, Elixir makes it easy enough to knock out in an hour or two (unless the API itself is a pain to work with, but that would apply to any language).

httpoison:1.8 (Cliente HTTP, para requisições)

Você pode encontrar a versão mais recente do HTTPoison em: https://hex.pm/packages/httpoison

Perhaps this thread has what you're looking for https://elixirforum.com/t/httpoison-post-multipart-with-more-form-than-the-file/4222/5 or try this GitHub issue https://github.com/edgurgel/httpoison/issues/237

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens

In order to publish the artifacts to GitHub, we need to create a personal access token from the GitHub developer settings page and add it to the environment variables section of the Travis CI repository. The same variable api_key is used in the deploy phase of our configuration.