Bad characters in CI_COMMIT_MESSAGE environment variable
Summary
I am trying to use the CI_COMMIT_MESSAGE environment variable in a JSON request body to create a GitHub release and there seems to be some bad characters that cause the request to be rejected with a 400 error.
My repository is pulled from GitHub, so not sure where the source of the bad data is.
Steps to reproduce
POST to https://api.github.com/repos/{owner}/{repo}/releases using the $CI_COMMIT_MESSAGE variable to populate text in the request body.
{ "tag_name": "v1.0.0", "target_commitish": "master", "name": "v1.0.0", "body": "$CI_COMMIT_MESSAGE", "draft": false, "prerelease": false }
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
The CI_COMMIT_MESSAGE environment variable appears to have an unknown whitespace character at the end, which is rejected by the GitHub API. API returns 400 bad request. Using hard-coded text in place of the environment variable works ok.
What is the expected correct behavior?
CI_COMMIT_MESSAGE environment variable contains a clean string that can be used in API requests.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)