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

add fork specific settings #1

Merged
merged 3 commits into from
Feb 21, 2024
Merged

add fork specific settings #1

merged 3 commits into from
Feb 21, 2024

Conversation

goapunk
Copy link
Contributor

@goapunk goapunk commented Feb 15, 2024

Tasks

  • PR name contains story or task reference
  • Documentation (docs and inline)
  • Tests (including n+1 and django_assert_num_queries where applicable)
  • Changelog

@goapunk goapunk requested a review from m4ra February 15, 2024 08:12
@goapunk goapunk force-pushed the jd-2024-02-fork-settings branch from 3242ec5 to 7bc1d8e Compare February 19, 2024 15:13
Copy link
Contributor

@m4ra m4ra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@goapunk your home dir is in the django translation files here too

@goapunk goapunk force-pushed the jd-2024-02-fork-settings branch from 7bc1d8e to fe02bad Compare February 21, 2024 15:28
- adjust ci
- add fork requirements.txt
- adjust deploy script
@goapunk goapunk force-pushed the jd-2024-02-fork-settings branch from fe02bad to ffe7bba Compare February 21, 2024 15:29
@goapunk goapunk requested a review from m4ra February 21, 2024 15:29
@goapunk
Copy link
Contributor Author

goapunk commented Feb 21, 2024

@goapunk your home dir is in the django translation files here too

should be gone now :/

@m4ra m4ra merged commit 5837803 into main Feb 21, 2024
3 checks passed
@m4ra m4ra deleted the jd-2024-02-fork-settings branch February 21, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants