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

merge from dev #405

Merged
merged 34 commits into from
Jul 24, 2024
Merged

merge from dev #405

merged 34 commits into from
Jul 24, 2024

Conversation

pavuchara
Copy link
Collaborator

No description provided.

pavuchara and others added 30 commits July 16, 2024 12:49
1. Now when you respond to a vacancy, the response and the vacancy are not deleted.
Now the status of the response and the vacancy itself simply changes.

2. Added read-only field datetime_closed.
The migration is irrelevant and breaks other migrations,
providing access to the database before formation.
The edits described in this migration have already been done manually.
For a new user and a user who has updated their profile,
the dataset_migration_applied flag now changes its meaning.
Now endpoin projects/{id}/responses/ returns full file info.
…_accompanying_file

PRO-350: full file info
…rticipants

feature/kick-project-participants
…_and_responce

PRO-343: Change logic on vacancy response
…gration_applied_field

PRO-347: Bug with dataset_migration_applied
…ors/functional

Refactor/new collaborators/functional
Added read-only field with response count.
…r_in_vacancy

PRO-336: responses number in vacancy
@sh1nkey sh1nkey merged commit 49b00f9 into master Jul 24, 2024
2 of 3 checks passed
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.

3 participants