Cleanup bootstrap-vue a little bit
What does this MR do?
chore(bootstrap-vue): Remove husky and git hooks
Otherwise running yarn install
inside the bootstrap-vue directory
fails because husky cannot find the .git
directory. Furthermore we do
not want it to mess with the top-level lefthook config
ci: Add bootstrap-vue CI jobs
chore(bootstrap-vue): Stop traversing up eslint from vendor dir
chore(bootstrap-vue): Remove bundlewatch
We are not interested in this part of the deployment tooling, so let's just remove it.
chore(bootstrap-vue): Remove scripts and dependencies related to releasing
We don't need to release bootstrap-vue, so let's remove these things.
chore(bootstrap-vue): Deduplicate dependencies
Wow. So much duplication.
chore(bootstrap-vue): Remove third-party integrations
Remove third-party integrations with GitHub Actions, Code Sandbox, Dependabot, etc. Also remove .browserslistrc because we have our own top-level config.
Remove changelogs and everything as well.
Screenshots or screen recordings
N/A
Integration merge requests
Not needed, because bootstrap-vue isn't utilized yet.
Does this MR meet the acceptance criteria?
This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.
Toggle the acceptance checklist
Conformity
-
Code review guidelines. -
GitLab UI's contributing guidelines. -
If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer. -
If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer. -
If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above). -
Added the ~"component:*"
label(s) if applicable.
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
Security reports checked/validated by a reviewer from the AppSec team
Accessibility
If this MR adds or modifies a component, take a few moments to review the following:
-
All actions and functionality can be done with a keyboard. -
Links, buttons, and controls have a visible focus state. -
All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label
for icons that have meaning or perform actions. -
Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false"
toaria-expanded="true"
when an accordion is expanded. -
Color combinations have sufficient contrast.