Skip to content

Add feature check to Lock button

Collen requested to merge ee-add-feature-check-for-file-lock into master

What does this MR do?

Checks if the instance's license supports the File Locking feature and hide's the Lock button if it doesn't.

Why was this MR needed?

File Locking is a Premium feature but the Lock button was being displayed on instances with a Starter license. When clicked the button did nothing.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • EE specific content should be in the top level /ee folder
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/5952

Merge request reports