What is the best way to integrate Gitlab issues and other events with a proprietary system for notifications without modifying the code.
1) Web hook does not seen to dispatch notification on issues.
2) I could read the database and implement the integration.
Any other options?
Web hook does not seen to dispatch notification on issues
Check again that asertion against the latest 6.4 release (and this pull request):
Project web hooks were extended with new types of events.
Web hooks can now also be triggered when an issue is created or a merge request is closed.
That may not cover all the issue events you want, but it is a start.
Related
So i'm designing a new application with Nodejs and packaging into an executable then putting a release in github, I want to be able to monitor how many people are using my executable?
I was thinking about creating an api server and my application just make a call to that API service but I thought there might be something already out there any help?
The easiest way is to connect third party services that do that. The most famous one is Google Analytics
You just need to create your developer account and embed a few lines of tracking code. After that you can see full info about your visitors including their location.
I have searched high and low, but I can't find anything telling me how to enable GitHub Vulnerability alerts through their API. I conversely can't find anything saying it's not supported.
Does anyone know where I can find the API documentation if it is supported, or can someone tell me it's not? I have just completed a migration to GitHub for my origination and we have ~750 repositories so enabling them all manually is... less than ideal.
we released an API for this scenario a while back, so you can now enable or disable security alerts in bulk using that. We also published a sample which calls that API for all the repositories in an organization.
API: https://developer.github.com/v3/previews/#enable-or-disable-vulnerability-alerts-for-a-repository
Sample: https://github.com/github/enable-security-alerts-sample
#Russ looks like it's only available according to the UI. I am in the same position in needing to enable this for a very large number of repos.
Take a look at: https://github.community/t5/GitHub-API-Development-and/Security-vulnerability-alerts/td-p/15846
I got this from my companies GitHub service rep:
Enable security vulnerability via API (v3 or v4)
I've raised this and currently in conversations with the team that is responsible for
this feature to see when this could be addressed. I have to say this
is an exception to the GitHub rule of API/Platform first. I apologise
for that.
I'm trying to integrate Pusher instead of SignalR into my .NET application. My application consists of .NET Core Web Api and WPF clients and they need to communicate via Web Sockets (besides obvious REST communication).
The thing is I'm confused which library I'm supposed to use. Like there's an official .NET library which is called pusher-http-dotnet. But its nuget package is called PusherServer which is very confusing. Is it supposed to work only as a server solution? Can I use it for WPF clients? Seems like not as I see a lot of Triggering examples and no Subscribing ones.
There's another library under Pusher-Community account which is called pusher-websocket-dotnet and its nuget package is published under name PusherClient. The good news it seems to have some subscribing api. The bad news is it has quite serious issues without any response.
I'm totally confused with Pusher .NET libraries.
Pusher libraries are split in to http libraries, for publishing events and authenticating private channels (usually running on a server); and websocket libraries, for subscribing to channels and binding to events (usually running on the client). See here for a comprehensive list. pusher-http-dotnet falls in to the former category, so doesn't provide subscribing functionality. pusher-websocket-dotnet is the websocket counterpart (with subscribing etc.) – it is a community library, and as a result development on it is slow and it is not as polished as the official libraries, but many people use it without issue.
I'm using Perforce's P4API.NET to programmatically submit a large branch operation and would like to be able to provide my users with some feedback.
When using the command-line p4 client, there's a -I option for getting progress reports. Is there any way to get these reports with the API?
I'm using r13.1 but can upgrade if necessary.
The progress reports are exposed in the C++ API via the ClientProgress class:
http://www.perforce.com/perforce/doc.current/manuals/p4api/chapter.methods.html#clientuser.createprogress
This was added to the C++ API in the 2012.2 release:
http://www.perforce.com/perforce/doc.current/user/p4apinotes.txt
Major new functionality in 2012.2
New ClientUserProgress class which shows Textual progress
indications. New methods in ClientUser (CreateProgress,
and ProgressIndicator). See api documentation for details.
but there is not an analogous interface yet in the .NET API.
What is a difference when sending push notifications using templates SendTemplateNotificationAsync vs native SendAppleNativeNotificationAsync?
In a back-end we keep a track of device types that users are using. But I don't see what is the point to send native, as template works fine.
Template are indeed a powerful feature, especially when used for personalization.
The disadvantage is that changing the platform-specific payload of a notification requires updating the registration.
Usually template registrations are a good fit for notifications that have always the same format and target multiple platforms
Using native notifications sending might enable you to easily target specific devices, however you can achieve the same goal by using Tags.
The bottom line is that I also see no real value in using the native notifications other than simplicity on the client side development.
I also wouldn't be surprised to find out that the Notifications Hub itself is using the templates to send the native notification (but that is of course an assumption of mine...)