Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2892
Hi @Hapcy, thanks for submitting this PR.
It's best to create a feature branch for each ticket rather than committing
to master. You can fix this by creating a branch (git checkout master ; git
checkout -b 5109_invalid_content_encoding_header_in_rest_api_responses) then
resetting master (git checkout master ; git reset --hard 7f1c76d^ ; git rebase
upstream/master) then rebasing against master (git checkout
5109_invalid_content_encoding_header_in_rest_api_responses ; git rebase master
; git push -f origin
5109_invalid_content_encoding_header_in_rest_api_responses).
Something like that. Make a copy of everything first.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
