We have moved our codebase and wiki to github. However the google code version still shows up really high on Google. Is there any way to do an auto redirect to github when people land on the Google code version?
I'm not sure how long this option has been available (it may be related to Google announcing they're shutting down Google Code), but you can now set a "project moved" flag which will provide all visitors to your Google Code project with a link to any other site, including GitHub.
Note: It doesn't appear that you can fully revert this setting, at least not at the time of my writing this, so be sure you really don't want to access anything from the Google Code project before setting it.
You can mark your project as moved on your admin page. If you change your mind, you can clear the setting by clicking the publish button.
Setting the "Project Moved" Flag
Once a project has been successfully exported to GitHub, you will want to update your project's homepage on Google Code to avoid confusion.
Some project owners simply update their project homepage's text to indicate it has moved to GitHub. For example subtext or bwapi.
Another option is to set the Google Code "project moved" flag. When set, attempts to access the project will take users to an interstitial page indicating the new project location. In the future, the page will automatically redirect to well-known project hosting services such as github.com.
To set the "project moved" flag, navigate to your project's advanced admin page, at https://code.google.com/p//adminAdvanced.
Once there, enter the new project home page URL under "project moved". For example: https://github.com/google/kythe. Finally click the "Project Moved" button.
If you need to "un-move" a project, you can go back to the /adminAdvanced page at a later time and click "Publish". This will restore your project to its original state, before the move.
Related
How do I edit the design (html, img, css) of the page hosted at [myapp].app.link? I have configured this in my Branch account configuration as the "Link Domain" for my app redirect.
This Branch.io help page seems to imply that the page is customizable: https://branch.io/what-is-applink/
As per Branch support: The page being referred to is called a Deepview. A Deepview is a mobile web splash page, hosted by Branch, that gives a preview of the in-app content behind a given Branch link.
For more information on the same, you can go through the documentation below:
https://help.branch.io/using-branch/docs/deepviews#overview
You can navigate to your Deepview setting from the Configuration page and then navigate to the Deepviews tab. You can not edit the existing Deepviews, however, you can create your own custom Deepview. Do go through the following documentation for a step by step guide:
https://help.branch.io/using-branch/docs/deepviews#1-enable-default-deepviews-templates
https://help.branch.io/using-branch/docs/deepviews#1a-create-a-custom-deepview-template
I have a Github repository with an associated Github page (say, github.com/user/mypage), and I would like to include the URL to the Github page (say, user.github.io/mypage) in the About section of the repository. When I go to "Edit repository details", the Github page already shows up in the "Website" field and cannot be changed (which is fine) but it is not displayed in the About section. I've tried this with multiple repositories with associated Github pages, and all show the same behavior. Am I overlooking something blatantly obvious, or is it just not possible to include the URL here?
I tried for a week to link my GitHub Page to my GitHub repository. I just figured out how to do it and then found this post. I thought I would go ahead and post my answer. Doing so might be helpful by making this question more visible in future internet search results.
Click on the gear icon in the upper-right of your GitHub repository to the right of the word "About" (shown in the red circle below):
Paste the URL of your GitHub Page into the Website bar in the window that pops up. This Website bar will already contain text that is grayed-out and might match the URL of your actual GitHub Page. That grayed-out text is inactive. Go ahead and paste in the URL of your GitHub Page anyway. Then click Save changes. You are done. Your GitHub Page should now be linked to your GitHub repository.
I am trying to host a web page from github. Namely, I am trying to do that with the page: https://github.com/oobarbazanoo/JS-BuyList.
I type to the address bar oobarbazanoo.github.io/JS-BuyList and nothing happens I just get an error.
What am I doing wrong?
In order to solve the problem follow these steps:
Go to you Repository.
At the top choose Settings.
Go to the GitHub Pages.
Choose the source you need and save it.
Wait a few minutes, then copy and paste web link which will be given in GitHub Pages section.
I want to make google voice actions app for my Google Home. But, based on quick research, as of Dec 11, google does not allow private projects for Google Home.
References:
Can I develop a private action only accessible via my google home or linked account?
How can I run my development action on my Google Home?
I understand that I can preview the app from API.ai project, and it deployes to the linked Google Home device.
But the issue is, the deployed app does not persist. It is no longer available after hour or so.
How can I make it permanent (if there is a way)?
UPDATE
Based on Leon's answer, I just wanted to extend the steps on how to enable the sample for 24 hours.
Click on the "Google Home Web Simulator" link on bottom right corner.
Then you will be presented with google home device - click on "Start" button on that page
On next page, top right corner you have the "ACTION PACKAGE" button Leon is talking about. Click on that and extend expiration time by clicking on "Preview for 24 hours" button. See screenshot below:
I have found a way to create the Action on API.ai and then preview it indefinitely.
From API.ai:
Open browser dev console (Network tab)
Go to Integrations
Turn on "Actions on Google" integration
Click "Authorize"
Click "Preview"
Inspect the XHR response from https://console.api.ai/api/agent/googleassistant/preview in the Network dev console
{
"status":{
"code":401,
"errorType":"unauthorized",
"errorDetails":"You are not authorized for this operation. ",
"webhookTimedOut":false
}
}
Copy/paste the content of the response into a file called action.json
Then, download and install the gactions CLI from here - gactions CLI and then run this command:
gactions preview --action_package action.json --preview_mins 9999999 \
--invocation_name [your_own_invocation_name_here]
The preview_mins value of 9999999 makes the preview effectively indefinite.
Here is a video demonstrating it:
As of today, May 17 2017, the highest voted answer to this question no longer works for new API.ai projects due to the upgrading of the Actions on Google SDK to v2. A similar methodology to #Brady's answer does work still, but they've made it more difficult in some ways (more information needs to be provided to Google, globally unique invocation name despite being a local only test), and better in others (gactions CLI docs now explicitly state that indefinitely timed previews are accepted, and actually is the default if not provided as a argument to the gactions test call).
Create your API.ai agent as normal.
Under the "Integrations" side menu, open the "Actions on Google" settings.
Select "Test" from the bottom of the dialog box that appears (you may need to jump through a few hoops here, signing in, authorizing account access, etc.)
This is where it gets a little different. You now need to create a project on the Actions on Google console. Create or import a project to the console.
The first required step is to supply an action package, which can come from either API.ai or the SDK directly. For API.ai, you have to go back to the Integrations page we were at and press "Update" on your Actions on Google settings. (On the previous version of the SDK, this was labeled "Deploy" and would have made your app public, but don't worry - all this does now is update the AoG console. You publish publicly from the AoG console later if desired).
This new console requires more information outright than was necessary before. I found that the "Assistant app name" can be whatever you want, but the "Pronunciation" is strictly limited to a few conditions (globally unique, reserved keywords, non-brand violating). I also found that I could still invoke using the app name and not just the pronunciation, but I suspect that will be fixed.
Once you've filled out all the necessary information, you can test
from API.ai. Return to the AoG settings menu in API.ai and retrieve
the response content from the HTTP request preview (just like in
#Brady's answer above). Here we hit another difference. The content
of the request response can't be used directly in the action.json
file as it is wrapped in another object. You want to use only the
object from the property actionPackage. (i.e. remove
{
"actionPackage":
from the beginning of the content and
}
from the end). You should end up with a object of a structure similar
to this (but maybe not exactly, it depends on the content of your
API.ai agent):
{
"actions": [...],
"types": [...],
"manifest": {...},
"conversations": {...}
}
Put this into your action.json file.
Execute the new gactions CLI command:
gactions test --project <your_project_name_from_aog_console> --action-package action.json
Enjoy your local v2 Actions on Google SDK project! And pray Google does not alter the deal any further...
I tried my best to recall what I had to do from memory, so there may be some mistakes in this write up. Hopefully this helps someone.
You can extend the time the development action can be previewed on the web simulator or Google Home device. After you preview the action from API.AI, click on the list of action packages in the web simulator. Then select the "Preview for 24 hours" link for your action package.
The "Settings" menu is supposed to be the last menu, just after the "Graphs" menu.
Not having the "Settings" menu interferes with my ability to set Webhooks.
And yes, this is my repo - I own it.
landing page of my test-repo-travis repo
I was having the same issue today. Eventually, I figured that I do not have enough permissions to access the repo settings because in my case the repo belongs to an 'organization' and even though I have read/write access to it, I am not the admin.
Make sure that you're logged in.
Ctrl+F5 was ineffective, at least in my case.
Clearing the cache and cookies is the nuclear option, and it worked - Although it hurts.
I double checked after the fact: the landing page issue I had was specific to my Chrome browser, at least in this case. The landing page, as displayed by my Firefox browser, was fine. Ditto for the Safari browser was fine.
Until today, I'd never heard of a case where a landing page rendering could be fixed by nuking cookies and cache.
It happened to me today. It turns out, I wasn't signed into GitHub. As soon as I signed in, the settings have become visible.
Happened to me today too, fixed by adding /settings to the repository link
EDIT: Notice this will only work, if you are the owner of the repository