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

Remove a Repository from Travis #987

Open
joshk opened this issue Mar 18, 2013 · 45 comments
Open

Remove a Repository from Travis #987

joshk opened this issue Mar 18, 2013 · 45 comments
Labels
feature-request locked This thread is locked, and won't automatically be closed

Comments

@joshk
Copy link
Contributor

joshk commented Mar 18, 2013

Pro customers, and Org users, request for us to remove repos from Travis time to time.

It would be good to add, under the cog, 'Archive'.

This would hide the repository until another build request comes through. We can also add to the service hook list, a marker to say it has been archived, and a button to unarchive.

@cwc
Copy link

cwc commented Mar 28, 2013

👍 I moved a repo from my personal account to an org, and would like to remove the personal one from Travis.

@steveyken
Copy link

👍 I have a build that failed and has since been removed from github... would be good to remove build status as well as the "My travis chrome bar" reports as failed. Perhaps projects that are removed from github could be automatically hidden until another build comes in?

@sarahhodne
Copy link
Contributor

From #1181:

It would be nice, if i delete a repo, that it will be also completely deleted from Travis.

Maybe we should auto-archive when we detect that a repository no longer exists on GitHub?

@steveyken
Copy link

sounds good to me! 👍

@giodamelio
Copy link

I too would like this functionality 👍

@mraxilus
Copy link

👍 agreed

@sveneisenschmidt
Copy link

👍

@DavidMikeSimon
Copy link

👍 This would be very handy

@remyleone
Copy link

👍

1 similar comment
@koorgoo
Copy link

koorgoo commented Nov 28, 2013

👍

@nomeata
Copy link

nomeata commented Dec 6, 2013

I think it should be auto-archived when it is disabled under “accounts”.

@sarahhodne
Copy link
Contributor

@nomeata Good suggestion. We have considered this, and I think the plan is to implement something similar to this, where we only display "active" repositories by default.

@J7mbo
Copy link

J7mbo commented Dec 19, 2013

👍 From a UX perspective, this seems like a no-brainer. I was searching for a while wondering "they can't have left this out, could they?". Looking forward to this being implemented.

@aahutsal
Copy link

👍

@roll
Copy link

roll commented Jan 8, 2014

If delete repository on GitHub and then recreate (push from local) there will be 2 same repos (when logged in) on https://travis-ci.org/profile (visually identical) and https://travis-ci.org/ (with different build history). It will be greate to have opportunity to hide/remove/archive deleted ones.

@janosrusiczki
Copy link

👍

1 similar comment
@ghost
Copy link

ghost commented Jan 28, 2014

👍

@natesholland
Copy link

Are there any plans to make this happen? I would love to see it implemented.

@joshk
Copy link
Contributor Author

joshk commented Jan 31, 2014

There are plans, but we are likely to wait until the UI changes we have in the works. I don't have an ETA to share at the moment sorry.

@iammichiel
Copy link

👍

@rob-momentumjs
Copy link

👍

I just found that the travis job for the old duplicate github repository was masking the new one, because they had the same url. This meant that the badge was pointing to the old build.

As a workaround, I renamed my github repository.

@GrahamCampbell
Copy link

You know you can contact support and ask nicely for them to remove data from travis if you really need to. It's a better solution to renaming repos.

@felipec
Copy link

felipec commented Apr 12, 2014

I don't understand, there's already a configuration for that in https://travis-ci.org/profile; if I turn it OFF, why am I still seeing it in "My Repositories".

I've even delete the repository from GitHub, it's still there.

Why?

@BanzaiMan
Copy link
Contributor

@felipec "OFF" means that builds are off.

@felipec
Copy link

felipec commented Apr 13, 2014

@felipec "OFF" means that builds are off.

Of course, but any normal person would think of OFF/ON as symmetrical operations, but in this case if I turn a repository ON, the builds will start, and I will never ever be able to remove it, not even with OFF.

ON turns A and B on, and OFF only turns B off. Very intuitive.

@sarahhodne
Copy link
Contributor

We have considered hiding a repository from the sidebar when turning the repository "off" in the repository list. I think the main reason we don't do that right now was because that field in the database wasn't always up to date or sometimes led to confusing behaviour?

@felipec
Copy link

felipec commented Apr 13, 2014

Even if the field is not up-to-date, and the user scratches his head as to why the repository is not there, he could simply go to the list of the repositories, see that it's off, and turn it on.

Besides, how useful is it to have a repository listed that is not being tested anyway (according to the database).

@murrekatt
Copy link

👍

@roidrage
Copy link
Contributor

roidrage commented May 6, 2014

Could we start by adding a deleted_at field to repositories and start checking that in the relevant queries?

@joshk
Copy link
Contributor Author

joshk commented May 6, 2014

A lot of our queries for finding repos to show look at the slug but not the permissions. If a repo is removed from GitHub then we remove the permission records on Travis, thus, if we check permission records correctly we should be able to improve what we show to users.

@roidrage
Copy link
Contributor

roidrage commented May 6, 2014

Sure, but we could enhance these queries to look for this flag as well, no? I think both approaches have merit, ideally, they'd be combined.

@joshk
Copy link
Contributor Author

joshk commented May 6, 2014

Sure, was not ruling out the deleted_at addition at all. I think combining both would be great.

On 6 May 2014 at 6:08:38 pm, Mathias Meyer (notifications@github.com) wrote:

Sure, but we could enhance these queries to look for this flag as well, no? I think both approaches have merit, ideally, they'd be combined.


Reply to this email directly or view it on GitHub.

@sebastianbrosch
Copy link

I have the same problem like @roll

If delete repository on GitHub and then recreate (push from local) there will be 2 same repos (when logged in) on https://travis-ci.org/profile (visually identical) and https://travis-ci.org/ (with different build history). It will be greate to have opportunity to hide/remove/archive deleted ones.

My new recreated project is failing because the old, on github removed, project was failing on the last build. It will be nice to remove repos on travis.

@anikalindtner
Copy link

hej @sebastianbrosch I've looked into your issue and it should be resolved :) Let me know, if you still are having problems!

@sebastianbrosch
Copy link

thx @anikalindtner great and fast support. The build status image shows failing but the last build (rebuild over travis-ci) was successfully. I will commit and push on weekend and look if the image will be changed.

@wmayner
Copy link

wmayner commented May 19, 2014

👍

@android-leha
Copy link

I have problem with repository count in left panel after removing.
2014-05-23 11-50-39

@ekryski
Copy link

ekryski commented May 26, 2014

Hey @anikalindtner. I also have the same issue as @sebastianbrosch for the report PetroFeed/roach. We have duplicate build projects in Travis.

@rocket-js
Copy link

I've got the same issue as @android-leha

@horsik
Copy link

horsik commented Jun 7, 2014

I'm also affected by the issue @android-leha described

@jdanbrown
Copy link

+1 for adding a way to remove repos from the "My Repositories" list.

@egeste
Copy link

egeste commented Jun 27, 2014

+1

1 similar comment
@endyjasmi
Copy link

+1

@denis-sokolov
Copy link

Can somebody please lock this issue to prevent all these +1s and "me-toos"?
@henrikhodne, @BanzaiMan, please.

@travis-ci travis-ci locked and limited conversation to collaborators Jun 28, 2014
@MariadeAnton
Copy link

There's a possible workaround:

  • Create a repo named the same way in GitHub
  • Sync in Travis CI without enabling it
  • Delete it again in GitHub

@DrTorte DrTorte added the locked This thread is locked, and won't automatically be closed label Apr 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request locked This thread is locked, and won't automatically be closed
Projects
None yet
Development

No branches or pull requests