New, unlabelled issues requiring attention

Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the issue triage workflow, we would like to ask you to:

1. Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE)
2. Add a type label
3. Add a team label
4. Add relevant subject labels
5. Mention relevant domain experts if the issue requires further attention

For the issues triaged please check off the box in front of the given issue.

• "Squash-Rebase-and-Merge" as an available action
• The markdown toolbar button tooltip is not using the default placement
• Gitlab ci node modules not installed properly test failing
• Check hash of the file in .gitlab-ci.yml when using include keyword
• Daily Digest Email Notifications
• Moved project which had public visibilityto a group with private visibility
• Group menu button not working in IE11
• /api/v4/:project_id/languages returning 500 for archived projects
• Docs feedback: Create Project Avatar field not clear
• search and sign in buttons hidden on narrow display
• Import repo from local Gogs server to new local Gitlab server
• See icons or number of approved in merge request list
• Repository configuration vs forks
• My contribution calendar cleared when access to the projects was taken from me.
• new issue and issue details return 500
• Create new file in repository
• Make git tags first class citizens for releases
• Merge request UI hook output is not showing.
• Update existing file in repository giving 400 error in rest template
• Reducing complexity in .gitlab-ci.yml files
• Improve issues list empty state when a filter is selected
• Artifacts (css, js) are not available (404) after they are generated via "yarn build"
• gitlab-managed-apps should be configurable as k8s namespace
• Automerge not working when rebase is needed.
• Bad project order in group page
• Pre-trigger manual actions
• AutoDeploy stalls at rollout.
• While running the gitlab-ce docker container with no-root user and mounted home volume, the container started failed.
• Broken icon on admin page
• link collision in 'Configuration of your jobs with .gitlab-ci.yml'

/cc @gitlab-org/issue-triage