Such a simple thing as renaming a GitHub repository via its settings page. Now the button labeled "Rename" is disabled when I try different new names. Any clue what is happening?
Solved. The issue was due to my browser not being supported. There was not errors nor alerts, so I could not figure this out at first. I could rename the repo using a different web browser.
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 have just created a new repository in GitHub and I wanted to change the Readme file, however the "Commit Changes" button is just greyed out, as shown below.
As well as this, when I click on "Preview" to view how it would look with Markdown, nothing happens, it just stays on the "Edit File" tab. Why is this not working?
Try disabling adblockers. I found this post on github community I tried toggling my adblockers and found it was ghostery breaking the site.
Edit: Ghostery specifically breaks the page by blocking Adobe Experience Cloud. This can be resolved by either setting the github site as trusted or by enabling that tracker on the github site (as I've done).
I know I can manually go to PR and uncheck Viewed. Is there a shortcut to uncheck on all files in the PR?
Found some relevant issues on GitHub
https://github.com/refined-github/refined-github/issues/2444
Why I want to do it?
To be able to see the comments and expand the cards which are collapsed because I manually marked viewed.
I tried Option+Click on Mac , didn't work for me.
Don't think the UI currently supports that. It looks like you need to tick, all checkboxes manually. Or come up with a JavaScript to find and click them for you.
Try that in your browser console.
document.getElementsByName("viewed").forEach(ch => {if(ch.checked) {ch.click()}})
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.
Is it possible to create new branch directly from Issue which is posted on Github? We have project hosted on Github with many issues, it would be easy for us just to click one button in Issue web interface and create new branch for it to start developing.
This is not possible directly from the issue interface. I can try to provide you some workarounds and maybe start a debate why one would want this feature:
Creating branches directly on the web interface
After you've noticed that you need to start working on an issue you can just go to the repository main page (keyboard shortcut gc) and create a branch with the name you want:
Chrome extensions
If this is a must for you, you can create a chrome extension that augments the UI and creates a branch directly from the Issues WebUI using the GitHub API. There's a lot of open source extensions that augment the default WebUI.
Is it the most efficient way to start a new feature?
I think this changes from developer to developer, but having worked with GitHub for 7 years using Issues I've never felt the need for this feature because unless it's a one line change that doesn't require local testing or compilation, I still want to get down to my command line and IDE. If I have to do that, I still have to at least git fetch to get the branch I just created directly through the issue interface. If that's the case I've always preferred to just look at the issue and run git checkout -b branch-name, optionally with git push if my team needs to see the branch.
Then the issue name wouldn't normally translate to a branch name, at least I wouldn't want that. So that option to create a branch from an issue would probably need to spin out a prompt to allow me to name the branch what I wanted.
This is just my personal opinion and nothing else, hope it helps :)
GitHub finally added this feature request to their roadmap.
Summary
The branch is the first thing a developer creates when the start
working on a new issue. Creating that association makes it really easy
for someone to then follow the work happening and keep everything
connected as they take their idea to code.
Intended Outcome
We want to help developers get started on work faster and signal to
their team where to find the code changes related to an issue. It
should also be really easy to then follow development to the pull
request without the user needing to do additional work to link
everything together.
How will it work?
From the issue page, a user can quickly create a branch with an
auto-generated or custom name that becomes associated with the issue.
They can then fetch the branch and switch to it in their development
environment and further development changes (such as commits and pull
requests) are automatically associated with the issue.
https://github.com/isaacs/github/issues/1125
Nope. You can subscribe this issue.
You could accomplish this by creating a small script.
I'd start by leveraging the Issues Event webhook. This will fire a JSON payload every time an issue is opened. When the webhook fires, your script can then create a new branch using the Create a Reference API endpoint. Note: URL must be formatted as heads/branch, not just branch.
There is an app that automatically creates branches for issues. You can install it here for free: https://github.com/marketplace/actions/create-issue-branch
If you want to create the branches manually instead of automatically:
It does not enable you (directly) to click on create branch from the issue. Instead you would have to write a comment in the issue consisting of: /cib. If you do that, it automatically creates the branch from the issue.
Please note I have no affiliation with the app.
Recently I saw that Github finally added this feature to its Issues Panel.
All you have to do is navigate to an Issue on Github and scroll down to the following section: