While I was editing README.md in one of my repositories, the process blocked somehow.
Since then, when I access that repository, status stays in 'Fetching latest commit… ' and I am not able to upload any files or edit them on the web.
The other repositories work. I do not have this repository on my computer (i have the files obviously), and the system does not allow me to clone it, not even delete it.
What can I do to regain access?
THOUGH DEFINITELY it does not the answer your question, but I want to post a solution for whom have the same problem but because of different reason.
For Forecomers having the issue
I had the same issue(just reached this question by googling), and I remembered disabling the javascript of my browser. Why don't you enable the javascript of your browser and refreshing the page? In my case the problem was solved after enabling javascript.
Related
I am doing this course on HTML, CSS, and Javascript for Web Developers on Coursera, as I am new to all this, and I have stumbled upon something that I think is very old information in the course, and not working anymore with the same tools as they have changed over time. So in this course we have the GitHub pages tool, which at that time could be used simply via the "deploy" button. Right now, the GitHub pages tool is disabled unless you create a branch, and it offers this GitHub Actions option under Build and Development, from where you can choose different workflows. By choosing any of them, you get the site deployed, but upon entering it, it gives 404 error. From my understanding, what's missing is the index.html file. How can you use the GitHub Actions tool to also have the index.html file and get rid of the error?
I have tried deploying from a branch, but I am missing valuable information on how to make that work.
I just started working on a project that was created with Nuxt and a CI pipeline using Cirlce CI that detects changes in the repository and upload files via SFTP to DreamHost.
We also have a netlify cms setup that sends .md files to the repository that are read and displayed on the page.
Now to the weird part.
Whenever I change something in the repository (push from my local repo, or use the cms) the changes appear on the site as they should. They correctly trigger a rebuild within circle.ci, which completes successfully and when I look at the live site they are present.
However when checking back a couple hours later they have dissapeared. The changes are still present in the github repository, but they are inconsistent with the state of the live page which has reverted to its previous state.
I can manually trigger rebuilds within circle.ci but the same thing occurs, i can see the changes for some time, then they dissapear.
I don't even know where to start looking for the problemect.
Any leads, or well aimed shots in the dark would be greatly appreciated, many thanks!
Edit.
I think this might be relevant: Every 12 hours we trigger a rebuild on the page, mostly to check for outdated content and deliver freshly rendered pages. When i checked the site index under the _nuxt pages, i see the following:
There are older versions of the scripts that are correct and new versions that are incorrect, those new versions are then referenced, resulting in the content being false.
Why are the automatic rebuilds 'overwriting' the old build?
Where can i find out more about those triggers?
OP's issue was mainly coming from the fact that the app was pulling from the wrong branch.
Fixing that one, did it.
Let me start by saying that I'm very new to this. I have little to no technical background, so this might just be a simple problem, or I did something I shouldn't have done. It's my first time using the command line and dealing with static pages.
I recently deployed my Hugo site to GitHub pages. I only changed the configuration file, and that's it. (I followed this and this.)
The site is now live at https://USERNAME.github.io/. It's still showing the content of my chosen theme.
A few hours after deploying, I edited some of the local markdown files and pushed the changes. However, the changes aren't reflected on the site.
Now that I realize it, GitHub only displays my site's "public" folder and not all of the files in my local folder.
So, my question is, how can I change and update my site content locally and make sure that the changes are shown on the live site?
Any help is appreciated. Thanks so much!
Well, I know this requirement sounds a little bit strange, but we, our team, want to build a website for the issue tracker of the repository.
The basic idea is:
for every issue, suppose that we have a page connected to the issue;
on the page, there will be a comment system, which is connected to the issue
posting comment on the page will actual become a comment to the issue
comments on the issue will be loaded on the page, when the page is opened by browsers.
That is to say, if we have pages connected to issues, respectively, for every specific pair of page and issue, comments on page and issue are equivalent. This is what we have done.
Now, the problem is how to deal with posting new issue. As you could see, the simple system depends on the connection between pages and issues. Hence, in the following situations, a page should be build and set automatically and correctly:
someone posts a new issue from the GitHub issue tracker;
someone posts a new issue from the website, and the issue has already been synchronized to the GitHub issue tracker (yes, this is what we have implemented).
We hope that this kind of task could be handled without any third-party server, which means that we do not want to run a new service on any other server host.
Any hints or clues will be appreciated.
I try to clone a repository from github, and every time, it makes the folder with the project name, it makes the .git folder, and then nothing happens, it just freezes.
Running Windows 7 32-bit
I can download a zip using https, but I want to use git.
I've set up git globals and so on. I suspect it may be an authentication problem, but I have no way of knowing. Does anyone have any ideas?
"Freezes" sounds definitely like a bug.
Indeed, keeping the UI responsive was one of the first design goal of GitHub for Windows (We've mashed up the elegant Caliburn.Micro with ReactiveUI to provide a responsive interface and to allow for greater testability.)
Short version:
send an email to support#github.com
Long version:
As stated by the GitHub for Windows launch blog post:
If you find a bug, submit it to support#github.com. Every email is read by a real person
More recently, xpaulbettsx, a GitHubber, even tweeted about this :
Support# is good for Anything you want to tell GitHub - bugs, features, high 5s; everything but security which go to security#