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.

Sign up for GitHub

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

Jump to bottom

Handle Force Pushed Repository #319

Closed
aballman opened this issue Aug 23, 2018 · 1 comment · Fixed by #495
Closed

Handle Force Pushed Repository #319

aballman opened this issue Aug 23, 2018 · 1 comment · Fixed by #495
Labels
P/Medium Priority: Medium T/Bug Type: Bug
Milestone
September 2018

Comments

@aballman
Copy link
Contributor

Describe the bug
We keep track of releases based off of commits. When a user force pushes the project they are working on, it rewrites commits.

[] 1. Find a way to deal with commits that no longer exist
[] 2. Find a way to pull down changes in gitsync without choking on force pushed branch
@aballman aballman added T/Bug Type: Bug P/Medium Priority: Medium labels Aug 23, 2018
@aballman aballman added this to the September 2018 milestone Aug 23, 2018
@aballman
Copy link
Contributor Author

aballman commented Jan 8, 2019

This is increasingly becoming an issue with people who are force push branches with a continuous deployment option enabled.

This was referenced Jul 22, 2019
Merged
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P/Medium Priority: Medium T/Bug Type: Bug
Projects
None yet
Milestone
September 2018
Development

Successfully merging a pull request may close this issue.

Handle forced pushed commits codeamp/circuit
1 participant
@aballman