Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/ngrok fix #13

Merged
merged 5 commits into from
Sep 12, 2024
Merged
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
4 changes: 2 additions & 2 deletions .envrc
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
# .envrc is used by direnv (if installed) to automatically load the devshell
use flake . --impure
# .envrc is used by direnv (if installed) to automatically load the devshell
use flake . --impure
38 changes: 19 additions & 19 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
# Description

[Link to Ticket](insert the link to your ticket inside the parenthesis here)

Please include a summary of the changes and the related issue. Please also
include relevant motivation, context, and images!

# How Has This Been Tested?

Please describe the tests that you ran to verify your changes. If they are unit
tests, provide the file name the tests are in. If they are not unit tests,
describe how you tested the change.

# Checklist

- [ ] I have performed a self-review of my code
- [ ] I have reached out to another developer to review my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] New and existing unit tests pass locally with my changes
# Description
[Link to Ticket](insert the link to your ticket inside the parenthesis here)
Please include a summary of the changes and the related issue. Please also
include relevant motivation, context, and images!
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. If they are unit
tests, provide the file name the tests are in. If they are not unit tests,
describe how you tested the change.
# Checklist
- [ ] I have performed a self-review of my code
- [ ] I have reached out to another developer to review my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] New and existing unit tests pass locally with my changes
38 changes: 21 additions & 17 deletions .github/workflows/es-lint.yml
Original file line number Diff line number Diff line change
@@ -1,17 +1,21 @@
name: frontend-lint

on:
pull_request:
branches:
- main

jobs:

frontend-lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Install frontend dependencies
run: make frontend-dep
- name: Run frontend linter
run: make frontend-lint
name: frontend-lint

on:
pull_request:
branches:
- main

jobs:

frontend-lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Install frontend dependencies
working-directory: ./frontend
run: npm install


- name: Run frontend linter
working-directory: ./frontend
run: npx eslint
52 changes: 26 additions & 26 deletions .github/workflows/golangci-lint.yml
Original file line number Diff line number Diff line change
@@ -1,27 +1,27 @@
name: golangci-lint
on:
push:
branches:
- main
- master
pull_request:

permissions:
contents: read
# Optional: allow read access to pull request. Use with `only-new-issues` option.
# pull-requests: read

jobs:
golangci:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v6
with:
working-directory: backend
name: golangci-lint
on:
push:
branches:
- main
- master
pull_request:
permissions:
contents: read
# Optional: allow read access to pull request. Use with `only-new-issues` option.
# pull-requests: read
jobs:
golangci:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v6
with:
working-directory: backend
version: v1.60
38 changes: 19 additions & 19 deletions .github/workflows/testing.yml
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
name: testing

on:
pull_request:
branches:
- main

jobs:
backend-test:
name: Run all backend tests
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3

- name: Run backend tests
run: make backend-test


name: testing
on:
pull_request:
branches:
- main
jobs:
backend-test:
name: Run all backend tests
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: Run backend tests
working-directory: ./backend
run: go test ./...
108 changes: 54 additions & 54 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,54 +1,54 @@
# Learn more https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files

# dependencies
node_modules/

# Expo
.expo/
dist/
web-build/

# Native
*.orig.*
*.jks
*.p8
*.p12
*.key
*.mobileprovision

# Metro
.metro-health-check*

# debug
npm-debug.*
yarn-debug.*
yarn-error.*

# macOS
.DS_Store
*.pem

# local env files
.env*.local
.env

# typescript
*.tsbuildinfo

# @generated expo-cli sync-2b81b286409207a5da26e14c78851eb30d8ccbdb
# The following patterns were generated by expo-cli

expo-env.d.ts
# @end expo-cli

# Supabase
.branches
.temp


# Nix
env-vars

# Generated by Nix devshell
.devenv/
.direnv/
# Learn more https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files
# dependencies
node_modules/
# Expo
.expo/
dist/
web-build/
# Native
*.orig.*
*.jks
*.p8
*.p12
*.key
*.mobileprovision
# Metro
.metro-health-check*
# debug
npm-debug.*
yarn-debug.*
yarn-error.*
# macOS
.DS_Store
*.pem
# local env files
.env*.local
.env
# typescript
*.tsbuildinfo
# @generated expo-cli sync-2b81b286409207a5da26e14c78851eb30d8ccbdb
# The following patterns were generated by expo-cli
expo-env.d.ts
# @end expo-cli
# Supabase
.branches
.temp
# Nix
env-vars
# Generated by Nix devshell
.devenv/
.direnv/
96 changes: 48 additions & 48 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,48 @@
# Contributing to Nightlife 🌃

# Package Managers

- Mac - [Homebrew](https://brew.sh/)
- Windows - get [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
- Linux (you know what you're doing)

Thank you for contributing to this project! Here’s a quick guide to help you get started.

## Workflow

1. **Create a Branch**
- Before starting work on a new feature or bugfix, create a new branch from `main`:
```sh
git checkout -b feature/<your-feature-name>
```

2. **Develop Your Feature**
- Make your changes in the new branch. Be sure to follow any coding standards and best practices.

3. **Open a Pull Request (PR)**
- Once your changes are ready, push your branch to the repository:
```sh
git push origin feature/<your-feature-name>
```
- Open a Pull Request (PR) against the `main` branch.

4. **Pass All Checks**
- Ensure that all CI checks (linting, tests, build, etc.) pass successfully on your PR.

5. **Request a Review**
- Request a review from one or more team members. You can do this in the "Reviewers" section on your PR page.

6. **Get Reviewed**
- Address any feedback and make necessary changes. Once approved, your PR is ready to be merged.

7. **Merge Your PR**
- If there are no conflicts, merge your changes into `main`.
- If conflicts arise, resolve them before merging.

## Additional Notes

- Make sure your branch is up to date with `main` before opening a PR.
- Write clear and concise commit messages.
- Keep your changes focused; avoid bundling multiple features or fixes in one PR.

That’s it! Happy coding!
# Contributing to Nightlife 🌃
# Package Managers
- Mac - [Homebrew](https://brew.sh/)
- Windows - get [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10)
- Linux (you know what you're doing)
Thank you for contributing to this project! Here’s a quick guide to help you get started.
## Workflow
1. **Create a Branch**
- Before starting work on a new feature or bugfix, create a new branch from `main`:
```sh
git checkout -b feature/<your-feature-name>
```
2. **Develop Your Feature**
- Make your changes in the new branch. Be sure to follow any coding standards and best practices.
3. **Open a Pull Request (PR)**
- Once your changes are ready, push your branch to the repository:
```sh
git push origin feature/<your-feature-name>
```
- Open a Pull Request (PR) against the `main` branch.
4. **Pass All Checks**
- Ensure that all CI checks (linting, tests, build, etc.) pass successfully on your PR.
5. **Request a Review**
- Request a review from one or more team members. You can do this in the "Reviewers" section on your PR page.
6. **Get Reviewed**
- Address any feedback and make necessary changes. Once approved, your PR is ready to be merged.
7. **Merge Your PR**
- If there are no conflicts, merge your changes into `main`.
- If conflicts arise, resolve them before merging.
## Additional Notes
- Make sure your branch is up to date with `main` before opening a PR.
- Write clear and concise commit messages.
- Keep your changes focused; avoid bundling multiple features or fixes in one PR.
That’s it! Happy coding!
Loading
Loading