Skip to content

Support rate limiting headers from GitLab API

What does this MR do?

GitLab client now respects rate limiting headers

Why was this MR needed?

The headers weren't respected at all

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Closes #4796 (closed)

Edited by Steve Xuereb

Merge request reports