Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
name: Bug report
about: Create a report to help us improve
title: '[BUG] '
labels: bug
assignees: ''
---

## Expected Behavior
<!-- A clear and concise description of what you expected to happen -->

## Actual Behavior
<!-- A clear and concise description of what actually happens -->

## Steps to Reproduce
1.
2.
3.

## Environment
- OS:
- Node_version:
- Python_version:
- FFmpeg_version:
- Browser (if applicable):
- Client version: (if relevant)

## Additional Context
<!-- Any other information about the problem here -->

## Screenshots or Logs
<!-- If applicable, add screenshots or logs that help explain your problem -->
35 changes: 35 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
name: Feature request
about: Suggest an idea for this project
title: '[FEATURE] '
labels: enhancement
assignees: ''
---

## Is your feature request related to a problem?
<!-- Please describe a clear and concise description of what the problem is. E.g. I'm always frustrated when [...] -->

## Is your feature request related to a use case?
<!-- If yes, describe what it would enable and why it would be beneficial -->

## Proposed Solution
<!-- A clear and concise description of what you want to happen -->

## Examples
<!-- If currently available examples, provide links. If not, describe how it would look -->

## Additional Context
<!-- Any other information here -->

## Use Cases
<!-- Use cases where this feature would be useful -->

## Workaround
<!-- Is there a workaround available? -->

## Alternatives Considered
<!-- Any other solutions you've considered -->

## Support for Platform
<!-- If this is a platform-specific feature, indicate which platforms -->

88 changes: 88 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
# Contributing to Encoding_Database

Thanks for your interest in contributing! This guide will help you get started.

## Development Setup

1. **Fork the repository** via GitHub and clone your fork:
```bash
gh repo clone oliverdougherC/Encoding_Database
cd Encoding_Database
git remote add upstream https://github.com/oliverdougherC/Encoding_Database.git
```

2. **Create a feature branch** from main:
```bash
git checkout -b feature/amazing-feature main
```

3. **Install dependencies**:
```bash
# Server
cd server
npm ci
npm run build

# Frontend
cd ../frontend
npm ci
npm run build

# Client (optional)
cd ../client
python -m venv ../.myenv
../.myenv/Scripts/pip install -r requirements.txt
```

4. **Make your changes** and test locally:
```bash
# Run server dev server
cd server
npm run dev

# Run frontend dev server (separate terminal)
cd frontend
npm run dev
```

## Code Quality Checks

Before submitting a PR, ensure all CI checks pass:

- `build-frontend` — Frontend build must succeed
- `build-server` — Server build must succeed
- `audit-node` — No critical npm vulnerabilities
- `audit-python` — No critical Python vulnerabilities

## Pull Request Process

1. **Commit your changes** with clear, descriptive commit messages following conventional commit format:
```bash
feat(client): add support for new encoder
fix(server): correct endpoint typo
docs(readme): update installation instructions
```

2. **Push your branch**:
```bash
git push origin feature/amazing-feature
```

3. **Open a Pull Request** via GitHub and fill in the PR template.

4. **Request reviews** from Oliver or other maintainers.

## Coding Standards

- **TypeScript/JavaScript**: Use strict TypeScript and functional programming patterns
- **Python**: Follow PEP 8 style guide
- **Testing**: Add tests when adding new functionality
- **Documentation**: Keep README and code comments updated

## Getting Help

- Open an issue if you encounter bugs or have questions
- Check existing discussions for similar topics
- Reach out to Oliver directly if you need help

Thanks again for contributing! 🎉
4 changes: 0 additions & 4 deletions frontend/next.config.ts
Original file line number Diff line number Diff line change
@@ -1,10 +1,6 @@
import type { NextConfig } from "next";

const nextConfig: NextConfig = {
// Skip ESLint during production builds (handled separately in CI)
eslint: {
ignoreDuringBuilds: true,
},
headers: async () => [
{
source: '/(.*)',
Expand Down
Loading
Loading