nextcloud/server

Cross check selected mimetypes in the workflows against our mapping file

Open

#3,753 opened on Mar 7, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PHP (34,953 stars) (4,865 forks)batch import
1. to developenhancementfeature: workflowsgood first issue

Description

Anything that is not in https://github.com/nextcloud/server/blob/ade91c8fe2e9230dea62cbf47a19cd5907646864/resources/config/mimetypemapping.dist.json will never be used, so we can avoid some pitfalls

Contributor guide

Tech stack
php
Domain
backend
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with MIME typesBasic PHP syntaxUnderstanding of CI workflows
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Review the file resources/config/mimetypemapping.dist.json referenced in the issue. Cross check the selected mimetypes used in the repository's CI workflows against this mapping file. Ensure every mimetype appearing in workflows exists in the mapping file. If discrepancies are found, either update the workflows to use only mapped mimetypes or add missing mimetypes to the mapping file. The issue does not specify which workflows, so identify them from the repository's CI configuration.