API for releasing actions to Github Marketplace - github

Is there an API or a programmatic way to release an action to Github Marketplace? Most actions/APIs are for creating a release in the Repo itself but releasing to marketplace seems like a UI only feature. Does anyone if there's an API or cli method for doing so?

It is true, as mentioned in GitHub Marketplace, that:
Anyone can publish an action in GitHub Marketplace as long as they meet the terms of service. Unlike apps, GitHub Actions listed in GitHub Marketplace are not verified by GitHub.
In that regard, the process could benefit from an API.
But while there is a GitHub Marketplace API, it does not include the publication process itself, which remains a manual process for now.

Related

Should GitHub Pages https:<moniker>.github.io/<repo> point to Read-the-docs build?

I have a GitHub repo of docs linked to my RTD account. The GitHub/RTD connection appears to be set up correctly with a functional webhook (green checks at both ends). Commits to the repo trigger a successful build on RTD as expected. RTD is an Authorized OAuth App and my RTD account is connected to my GitHub account.
Under Settings -> GitHub pages, I have tried both master branch and master branch/docs. I would expect https://moniker.github.io/repo-name/ to go to the connected RTD docs. But it just shows the repo-name/README.md file, not the repo-name.rtfd.io docs. Am I misunderstanding the linkage or the use of GitHub Pages? Or am I completely missing something? Thanks for any insight.
I put in a help desk question to GitHub and their response was:
GitHub Pages provides its own web hosting and will not integrate with external services. If you're publishing your site elsewhere GitHub Pages will not link to it.
So the answer is "no", adding the webhook only triggers a new build on commits and I do explicitly need a docs/index.html (or .md) that redirects to the RTD documentation.

How do I disable a Github check for Google Cloud Build

I've installed the Google Cloud Build app from Github Marketplace, and enabled it on several repositories, only to discover that enabling access for those repositories automatically starts running the Google Cloud Build "check" after every PR or push to a PR. Since some of those repositories are not actually ready for Google Cloud build, I needed to turn off the checks... I used the URL mentioned in the docs to get to the page where you can select which repositories should be connected to your GCP project, and unchecked a bunch of them... this disconnected them from the project, but, surprisingly, did not disable the Github checks! So now, there are Github checks on several repositories that just result in an error because they're not connected to any projects in Cloud Build.
Surely, it is not an uncommon use case to need a way to "disable Checks" on a per-repository basis - is there any way to do that?
(If not, consider it a requested feature if there are any Google Engineers reading!) ;)
I did talk to chat support, and the only way we could figure out to remove the checks would be to uninstall Google Cloud Build completely from the entire organization, which I don't want to do because we do have some setup that I want to keep, and I don't know how much of that configuration would have to be redone if I uninstalled it completely.
Here is a screenshot of the broken check that I can't disable:
I think there are 2 steps to disable CloudBuild,
1. Disable on CloudBuild itself. For some time I kept seeing 2 builds per push made, but disabling a trigger on CloudBuild helped fix that.
2. On Github, you can configure the Cloudbuild app to monitor a specific repo on the organization level setting.
3. If you feel a lot adventurous though and it's not solved, on the project level setting, you could delete the Webhooks integration for cloudbuild, as that's what Github notifies of each build.
It can be found within GH App installations:
https://console.cloud.google.com/gcb-github-registration
Select the GH account used for your link between Cloud Build and GH, then the GCP project you want to edit.
Here connected repositories can be edited, and in the second step (Trigger settings), the "Default GitHub Checks" can be disabled.
You can also goto settings of your repository and click installations inside settings.
And then remove Google cloud build from Installed apps and authorized github apps.
Cloud Build Triggers are still in beta, and have gone through several updates since this question was posted, but it now appears that the "Github Default Checks" are no longer hidden from management. They are now explicitly offered (but not automatically created) when connecting a repo, and you can finally view and disable (or delete) individual "Github Default Checks" on the trigger management page: https://console.cloud.google.com/cloud-build/triggers
I'll leave this as unanswered, because I'm uncertain this is how it is working for everyone, or that this answer will remain true, but if it works for you, feel free to vote up the answer!
To link GCP Project to the Github repository, create a trigger by clicking on resolve link, besides Action Required and then disable the same. For me this procedure worked out.

Replacing Github email service with Webhooks

Right now we are using the Github email service so that our team receives notifications whenever changes are made. However, soon Github services will be deprecated. I was wondering if there was any pre existing services that could replicate the behavior that the Github email service produced. This would save us a lot of time and we wouldn't have to run a server just for handling this one webhook.
Thanks
As recently (Nov. 2018) confirmed in "GitHub Services Brownout Updates and Timeline", GitHub services (like email notification) will disappear in January 2019.
The original annoucement suggested to replace them with webhooks.
The intention of GitHub Services was to allow third-party developers to submit code for integrating with their services, but this functionality has been superseded by GitHub Apps and webhooks.
In addition, check out GitHub Actions, still in beta but which have potential.
There are efforts made to look for a webhook-based alternative in the meantime. As in for instance pyinstaller/pyinstaller issue 3579. But no clear answer yet.
Update Feb. 2020: this issue is now closed. And GitHub Actions are no longer in beta.

Jira Issues (User Stories) integrated with GIT Issues (Developer Tasks)

All,
How do you associate a GitHub issue (developer task) to a Jira issue (user story).
And how do you configure Jira to have full visibility into GitHub issue status, and commits?
As background, we currently use Jira Cloud.
JIRA integrates with Atlassian Stash. You can set up integrations to change the status of the JIRA according to things like when a pull request is opened or merged. You will also have links from the JIRA page to see the individual commits. See the JIRA INTEGRATION section on the link.

JIRA GitHub Integration in an online hosted jira solution

I know there is a github jira plugin, which is a .jar https://github.com/atlassian/jira-github-connector-plugin , how do I add this to an online hosted jira solution.
Basically we'd like to see commit activity, update time in jira tickets with a github commit message and the "source" tab should show github project rather than the default svn that jira provides.
Regards,
Noj.
Came across this question today while searching, figured I would add in the link from Jira. Must not have been available at the time this question was asked.
https://confluence.atlassian.com/display/JIRASTUDIO/Integrating+GitHub+with+JIRA+Studio
If you're talking about JIRA Studio, they do not support any plugins except the ones they provide:
http://confluence.atlassian.com/display/JIRASTUDIO/JIRA+Studio+Plugin+Policy