I've uploaded a Github Gist and I've set it to be secret.
Now I want to change the gist to public, but I can't find how to set it public.
Could anyone help me about that?
I upload a Gist code and set it to be secret.
Now I want to change the gist to public, but I can't find how to set it public.
Since May, 9th 2014, it is possible: "Change the visibility of your Gists"
You can change the visibility of your Gists whenever you want.
When editing a Gist you'll now notice a new option to toggle the visibility between Public and Secret.
The URL for your Gist will never change, just its visibility.
As commented by GiDo though, since 2016:
you can only make public a gist that was previously private.
When it is public it will stay public.
This is confirmed in "Creating gists"
After creating a gist, you cannot convert it from public to secret.
Update:
You can still convert a secret gist to a public gist by first selecting "Edit" -> "Make Public". This feature has been partially rolled back, however, since 12/15/16 and you will no longer be able to switch it back to secret.
From the docs:
After creating a gist, you cannot convert it from public to secret.
Correction; this information is outdated. See VonC's answer from May 9, 2014.
Original answer:
No, you'll have to create a new public gist and copy/paste the contents.
If you want to preserve all of the history of the original secret gist, Chris Dzombak has written an article walking you through how to clone a gist, step-by-step, to preserve its change history.
Related
When defining a link like this
[description](ftp://user:pw#host/...)
or simply
ftp://user:pw#host/...
Azure DevOps turns the colon between user and pw into a slash. In other words, the effective user name when clicking the link will be user/pw, with no password set.
Is there a way to prevent AzDO from doing that?
As a workaround, I'm now using backticks:
`ftp://user:pw#host/...`
which keeps the url unchanged, but a) it is not turned into a clickable link and b) I cannot use a description text to be displayed in place of the link.
Update: What I'm trying to do is fine according to CommonMark, an attempt to create an unambiguous specification of Markdown, that has been adopted by the likes of GitHub and StackOverflow:
Update>>By reference to this doc: About Wikis, READMEs, and Markdown, wiki uses Markdown format.
Testing in Markdown online and found that this
[description](ftp://user:pw#host/...) will show link content ftp://user:pw#host/.... However, it shows ftp://user/pw#host/... in Azure DevOps wiki page, so this issue can be reproduced.
It might be caused by Azure DevOps security consideration, I suggest that you could submit this issue here, so the product group will investigate it further. Thanks for your feedback.
I want to create a public gist in GitHub. I've been on YouTube and in Google search but have not found an answer to this question. And I don't see an answer in Stackoverflow to this question. This my seem trivial to some of you but I'm not so savvy in the tech world. I have a GitHub account. I did the tutorial in the Read Me Guide where I learned about repositories, branch, commit and pull request. I was in StackExchange chat room where someone asked me to make a public gist of my code that I was asking help with. Now I want to create a public gist of my code. On the Gist page I see a place to where I think the code is suppose to go. I see an Add File tab. But nothing happens when I click on it.The app won't let me just paste in my code. I see a place for a gist description. And I see a place for a file name including extension. But how do I place my code to create a public gist? Where does it go? Somebody help, please. After some more searching I think I got an answer. A Gist is just a repository. Am I right or wrong?
Assuming that you are logged in on GitHub:
Visit the Gist page
Paste your code in the text box directly underneath where it lets you set a file name;
Then press 'create public gist' in the bottom right.
For more information on this, visit the official docs.
If you want to create public gist repository on github then following steps are there,
There is a GithubHist(https://gist.github.com/) available to share you code publicly over the internet.
One of the advantage to use this is that when you create repository in GithubHist, one same repository will be created on https://bl.ocks.org
This will run your code and show output to the user.
Steps to use GithubHist
Login on Github.
There is a Gist option on top of then menu. Click on this.
It will redirect you on https://gist.github.com/
Here in Gist description give Title of your project.
Now create index.html file. This file runs by default when you go on https://bl.ocks.org with your repository location.
Now you can add as many files that you need in your project here.Just click on add file.
To add License,you need to add license.txt file and add contents of the license.
At last click on “Create public gist” or “Create Secret gist” option at bottom.
To add Background image of your project on https://bl.ocks.org
Get git clone of project to your local machine.
Create file with name “thumbnail.png” with dimension 230px * 120px.
Add this file to your project.
Commit and Push changes.
It’s Done now.
Check your Project with links
https://gist.github.com/yourName/ProjectId Source of project
https://bl.ocks.org/yourName/ProjectId output of project with source
Please see my blog on medium
https://medium.com/#thakkarchintu5/using-githubgist-on-github-f4f0944bbc80
also check gist repository that I have created
https://bl.ocks.org/ChandrakantThakkarDigiCorp
Until recently I was able to find all my public comments using a link on my profile page. I was using this functionality to keep track of all issues where I have commented, but not contributed anything. It was under a section called "Public Activity".
This function seems to have been removed. I can not find anything about it on the help page about profiles.
Does anybody have any information on when and why this was removed?
You can do this with an advanced search query. In the Issues search box, enter "commenter:username".
Or if you want to search a specific repo: "RepositoryName commenter:username".
This link is quite useful, it's a live feed of all issues you've commented.
https://github.com/notifications/subscriptions?reason=comment
Alternatively, this link is also helpful and is probably what the OP asked (issues where one has written comments):
https://github.com/search?l=&q=commenter%3AVadorequest+is%3Aissue&type=issues
Replace "Vadorequest" by the username you're looking for
You can also use the global search with commenter:Vadorequest is:issue to achieve the same result
Also, if you want to track discussions you participated in, this link might help:
https://github.com/search?l=&q=commenter%3AVadorequest&type=discussions
Replace "Vadorequest" by the username you're looking for
You can also use the global search with commenter:Vadorequest to achieve the same result
This 4th (and last) is not related to the OP's question, but might come in handy. It lists all PR you were requested as reviewer.
https://github.com/notifications/subscriptions?reason=review_requested
Type involves:<username> in the search box on the GitHub's main page. This will find all the issues that the specified user commented on, was assigned to or mentioned in.
For example, if the user's name on GitHub is unclebob, the search query should look like:
involves:unclebob
Or when searching information about yourself if you're logged in to GitHub, simply:
involves:#me
Note, that unlike involves similar search qualifiers - author and commenter - will omit certain results from the search:
author will find only the issues that were started by the user; if the specified user comments on the issue that was started by someone else, author query won't return it in the search results.
E.g., compare involves:unclebob and author:unclebob type:issue.
commenter will find only those issues where the specified user commented second or later (creator of the first comment in an issue is considered its author and not a commenter); if the user starts an issue and then never comments on it, the commenter query won't return it in the search results.
E.g., compare involves:unclebob and commenter:unclebob.
In other words, when it comes to searching comments, author and commenter return only a subset of involves' results. So I recommend using involves not to miss anything.
Since GitHub Universe 2016, the profile page has changed.
It still has a "Contribution activity" though, which includes your own comments. But you might need to click on "Show more activity" to see past the last few weeks.
And you can email yourself your own activity since last June: "Email updates about your own activity".
If you want a list of all issues where you either created them or were a commenter on them, this link works best:
https://github.com/notifications/subscriptions?reason=author,comment
I want to find all the GitHub issues that I commented on. I tried searching for commenter:mbigras type:issue like the Searching issues and pull requests GitHub article suggests. But that method returns fewer results than the public activity section of my profile.
See both attached images:
Search method
Doesn't display current results:
Profile method
Gets mixed up with other public activity:
Is there a way to get the full history of my comments on GitHub?
EDIT
author:mbigras type:issue gives wider results but still not the full history:
What I'm looking for is a way to quickly view all my comment/issue history in all issues.
EDIT
I emailed GitHub about this. Search doesn't match the public activity section because search indexes issues by creation date and not last active date.
How do you keep organized about which issues you've commented on?
Search for commenter:username in the main Github search box.
For example commenter:gavinandresen
To see recent activity, select Recently updated from Sort dropdown
You can also narrow the search: is:issue commenter:gavinandresen
I have also been very frustrated when I could not find an issue that I have commented on a while ago. I even did not remember the project it was in. I knew only the problem I was referring to.
Then, I went to the Notification settings on Github and saw there is an Include your own updates option that is unchecked by default.
Once you check it, Github will send you an e-mail notification about every comment or PR you make. They you probably want to add an appropriate label and filter for emails so Github messages do not clutter an inbox.
My life has changed since then. Now, every time I want to find something I have written on Github, I just search for it in the e-mail notifications.
You can view all the issues on Github you have commented on by going to https://github.com/notifications/subscriptions and selecting Reason as Comment.
This will show all the issues that you've commented on.
You can also filter the issues by selecting other reason such as Assign, Author, Manual, Mention, etc. but you can select only one reason at a time. Also, you can filter the issues by repository by selecting the concerned repository from dropdown after clicking Repository
Search All GitHub using the search term is:issue author:#me
You can also check the following links.
For all your subscriptions
https://github.com/notifications/subscriptions
For all your issues
https://github.com/issues
For all your pull requests
https://github.com/pulls
In case someone is interested to know how to find these links, go to github's resi api documentation. The URL's are not explicitly described there. However, look for the page names bellow REFERENCE.
If you lowercase the relevant word (for example Issues become issues, Pulls become pulls) and put that after https://github.com/, you most probably will find what you are looking for.
This might be a little late, but there's also another way to find what issues/PRs you have participated in. This method also brings in a lot more things you might be interested in too!
When you are on the website main page, on github.com, use the keyboard shortcuts as described here to open your pull requests or issues. The shortcut for these is in particular [g, i] for issues and [g, p] for pull requests (I remember g by go, but whatever works for you.)
After you go to the page directed by these shortcuts you are greeted by an entire screen of goodies you can use! The search bar can be edited and the buttons can be used to make your experience fast!
Type involves:<your username> in the search box on the GitHub's main page. This will find all the issues that you commented on, was assigned to or mentioned in.
For example, if your username on GitHub is unclebob, the search query should look like:
involves:unclebob
Or if you're logged in to GitHub, then simply:
involves:#me
Note the difference between involves and similar search qualifiers - author and commenter:
author will find only the issues that were started by you; if you comment on the issue that was started by someone else, author query won't return it in the search results.
E.g., compare involves:unclebob and author:unclebob type:issue.
commenter will find only those issues where you commented second or later (creator of the first comment in an issue is considered its author and not a commenter); if you start an issue and then never comment on it, the commenter query won't return it in the search results.
E.g., compare involves:unclebob and commenter:unclebob.
In other words, when it comes to searching comments, author and commenter return only a subset of involves' results. So I recommend using involves not to miss anything.
Also, since Github is on the web, any HTTP search engine works, eg Google, Bing, etc. This works to the extent of your search engine's quality and the uniqueness of the writer name.
(Indeed, I actually do this all the time when I need to find any previously written web (engine)-accessible publication, including those on StackExchange. Names I use are 1 in probably an infinity, so Google often works better than forum search options.)
(Sample Google link.)
If you want to search for multiple users in a single search, use it like in the global search bar without the OR logical conjugation:
commenter:FantomX1 commenter:FantomX1-github
since the similar google way approach with 'OR' would not work
commenter:FantomX1 OR commenter:FantomX1-github
Is there a way I can remove a gist on GitHub? Created a gist earlier, but don't really want it there anymore.
Currently:
There's a "delete" button at the top of each gist now:
Previously...
Previously there was "delete this gist" link at the bottom of the gist's page, as below - thanks to Daniel Smith for pointing out in the comments below that this has been changed.
I created a tool which can help you delete multiple github gists both secret and public gists at once. https://gist-cleaner.ndolestudio.com
It's open source, you can find the source code here https://github.com/NdoleStudio/gist-cleaner