I'm using the Github applications for Windows for 2 accounts.
One is my personal and the other one is a professional account.
The problem is that everytime I logout and login (depending on which project I'm working on) Github sends me an email that a new ssh key pair has been generated for this computer.
I tried to unsubscribe from these mails or even setup a fixed multiple key pair but to no avail.
Any tips?
It is not intended by GitHub to have several User-Accounts for different needs. Ususally you have only one User-Account and use the collaborative-features on repositories to work together.
In a professional context you'd use GitHub's organizations to create teams for the specific repositories - where every team-member uses its one and only GH-account.
However, to use different GitHub-accounts you may try to use the Git CLI as described here or a different Git GUI (Sourcetree seems to provide a kind of multiple account-management).
Related
My Teams app:
multi-tenant
deployed using Teams Toolkit to Azure Storage, CDN enabled with a Custom Domain
in alpha use by internationally distributed organisation (third party, not me), users around the world
the app functionality works fine including multi-tenant
in rapid development so frequent code updates. Very rare manifest updates.
Problem:
I frequently update the app's code and deploy the update to Azure using Teams Toolkit
when I do this users often report 'blank tabs' for a period of time, can be many hours. They see the tab menu but the tab contents are simply blank. Purging the CDN doesn't seem to help.
seems most common using Teams desktop app but also reported using browser and mobile Teams app
I think this may be an issue of code deployment .js files (each of which gets a new filename) not being available to the install, I can sometimes reproduce but very unreliably. Other times I can access the app, using a user account on the client's AAD, successfully from different locations (using a VPN to emulate location).
Previously the app's Custom Domain was managed on Cloudflare's proxy.
I disabled this and implemented Azure CDN.
Users continue to report the problem.
This is very poor user experience.
Does anyone have experience of this or hypotheses on what may be happening?
Thanks.
Would suggest to test one thing first: manually deploy a new code change to Azure storage, with the same storage-CDN-custom domain setup.
See if this also causes the hours delay symptom.
By doing this, if the issue is reproducible, it may indicate that the Azure Storage-CDN configuration needs to be optimized.
Otherwise please share the result and it will help narrow down the root causes.
I joined a team that has 100+ repositories on GitHub and the watch default setting is ON. I just need it on a handful of repositories. Is there any way to change this setting for all repos without using the web UI and changing it one at a time?
Not that I know of.
In that kind of use case, I would create a second account, and monitor only the few repositories I need from said second account.
That way, I don't have to fiddle with the existing settings for the first account.
Is there a way to view repository traffic for all repositories on your account at the same time? (without creating your own custom dashboard using the Github API). It would be very convenient. I suspect a bash script might do this without too much effort (e.g. get all repo names, get the traffic/stars stats for each repo in the list). But I want to be sure something obvious doesn't already exist before writing anything myself
I am not ware of any native dashboard that would aggregate multiple GitHub repositories into one convenient view.
You would therefore have to rely on third-party scripts, such as, for example, nchah/github-traffic-stats (Python)
Get statistics on web traffic to your GitHub repositories.
Since it is limited to the last two weeks, you might have to record those statitics over time (example: Microsoft/GitHubTelemetryParsor)
I would like to synchronize two Confluence spaces that exist in two different environments. The logic behind is the following:
We want to have an internal draft space that the client can't see and an external space (client space) where can push our validated content to.
Is such thing possible with Confluence plug-ins?
I already found the Comala publishing plug-in but I don't think it supports spaces that are located in an external environment.
You can combine Comala Workflows (paid add-on) with Comala Workflows - Remote Publishing (free add-on that requires Comala Workflows) for doing so. In draft space (source Confluence instance) you set up a simple workflow, which publishes the approved pages to the external space (target client instance).
Give it a try and drop us a line in case you have troubles (support).
Disclaimer: I work in Comalatech, the company behind those add-ons.
Regards,
Gorka
We are currently using Freshdesk for our customer support and GitHub for our code. On receiving a bug or an improvement feature request via Freshdesk, we would like to forward that ticket (with all the details + screenshots) to an email in GitHub so an issue is created automatically on GitHub. That would save us a manual entry.
Look forward to an advice on this or a better solution.
NOTE: Had come across https://zapier.com/zapbook/gmail/github/72/create-github-issue-email , but we would prefer a direct interaction without a third-party app in between.
Creating an issue to GitHub wouldn't be done by "sending an email", but only by using the GitHub v3 issue API (like this script, for example, to migrate issues to GitHub)
That means in your case having a trigger on FreshDesk (or an "Observer" to call a webhook) which would parse the ticket and create the appropriate bug report on GitHub.
From the Observer/WebHook help page:
Webhooks also come handy when you want to trigger an action in an external application or tool (as well as some updates that the Observer can't perform, like update time entry on a ticket or add a note to a ticket)
You would manage that webhook locally on your side, and that callback would in turn call the right GitHub API commands to create the GitHub issue.
We had similar needs and built a very simple tool to let anyone in the team send/forward emails to create GitHub issues. We were using it internally at first so that non engineering team members didn't have to go to GitHub to create issues. We just made it available to anyone (and free). It supports attachments.
You can find it at https://fire.fundersclub.com.