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

refactor: Unshare file #70

Merged
merged 1 commit into from
Oct 18, 2023
Merged

refactor: Unshare file #70

merged 1 commit into from
Oct 18, 2023

Conversation

AndreaVelasquezA
Copy link
Member

Endpoint to unshare file using token, other user's name, and file id.

Endpoint to unshare file using token, other user's name, and file id.
Copy link
Contributor

@PedroChaparro PedroChaparro left a comment

Choose a reason for hiding this comment

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

Squash and merge :octocat:

@PedroChaparro PedroChaparro changed the title Feat: unshare file refactor: Unshare file Oct 18, 2023
@PedroChaparro
Copy link
Contributor

You used the right commit type (feat) in the Pull Request name. I'm just changing it to refactor to prevent the project version from being increased twice for each endpoint, as you're creating one PR for the controller and another for the view and tests.

You can use feat in the next PR when this controller is called from the view and the endpoint is fully functional.

@AndreaVelasquezA
Copy link
Member Author

I understand, I want to ask you when doing the merge, should I change the feat for the refactor, or in this case there is no problem

image

@PedroChaparro
Copy link
Contributor

PedroChaparro commented Oct 18, 2023

I understand, I want to ask you when doing the merge, should I change the feat for the refactor, or in this case there is no problem

Yes, you should change it to refactor. You can use the PR name to make it easier:

image

@AndreaVelasquezA AndreaVelasquezA merged commit eb70124 into dev Oct 18, 2023
@PedroChaparro PedroChaparro deleted the feat/unshare_file branch October 18, 2023 19:11
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