I'm authoring a tiny utility lib to supply argument parsers for gerrit hooks, but have stumbled upon a flag that I can't figure out.
The comment-added hook supports --<approval-category-id> flags, but I am not sure about where to find the IDs.
I'm quite confident that they relate to the Review labels available (verify, reviewed), but their documentation mentions nothing about an ID.
Anyone know where I can find these ?
Hook flag documentation here
Gerrit Review label documentation here
approval-category-id is the same as the "Review labels" defined here. They can be "Code-Review", "Verified" or any other you have customized.
The documentation of the hooks is a bit lacking. I've opened an issue upstream to improve this:
Hooks plugin's documentation lacks enough information about the hook parameters
Related
How to create a new project through Quire API? I can't find it in the documentation.
No, as of now this function is not implemented (and not included in the api-documentation accordingly).
If this is an important feature for you, you can propose a feature on github so others can vote for it as well. (Please only post specific bugs or feature requests there, for usage questions stackoverflow is the preferred forum)
So I know that GitLab pages can be employed to generate a static website from a project's repository. What I'd like to do however, is generate a static site from a project's wiki, which is a separate repository.
I also know that I could hook a static site generator to the webhook event for notifying wiki changes. I am trying to work out if this obvious (to me) use-case was anticipated and made possible via GitLab's pages feature, which has a simpler set-up, or if I really do need to resort to webhooks.
So far as I can tell, it wasn't, and I do, but possibly there are ways which just haven't been well described anywhere I can find.
Finally: the reason I want to do this is, GitLab's wiki seems to have a UI tailored to make it work more like a wiki than the repository's UI. This will I hope make it more useful/less hostile to the potentially non-technical users I foresee using it.
I don't think this feature is available yet, even though it would definitely be very useful.
You could try the following workaround:
Set up your project wiki's repository as an external repository.
https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/
This will setup repository mirroring, enabling automatic pull updates from your wiki repository to a new regular GitLab project repository. You can then use the regular GitLab CI and GitLab Pages feature to generate a static site from the wiki.
More information about repository mirroring:
https://docs.gitlab.com/ee/workflow/repository_mirroring.html
Example Project (Edit)
I have now made a basic (open-source) example for doing this, it actually works very well, you can browse its source and have a look at the wiki at https://gitlab.com/tkainrad/wiki2docs.
The generated site is located at https://tkainrad.gitlab.io/wiki2docs
You might even find that having a layer between your Wiki and the actual live site is useful.
This workaround together with GitLab Pages provides a lot of possibilities, and enables completely free hosting of wiki or documentation sites, while maintaining an easy EDIT-interface for non-technical contributors.
I am working with Azure Templates (ARM). I have to create a lot of resources and I will like to use some function to check what is going to be change in my infrastructure.
I searched a lot for any information related with this GREAT FEATURE (if there is one) but I did not find anything. So I will like to know if there is any way to see which resources are going to be change . I know about this for Chef and Ansible. So any suggestions or clue would be great.
No, unfortunately there is no feature to see that, but you should supply that to the feedback site. This is indeed a great idea.
Is it possible to notify a Trac installation about new revisions by calling a URL?
I have that GitLab server that allows me to trigger WebHooks when new revisions were pushed. Is there an interface on my Trac server that I could call in order to notify about the new revisions?
I agree with RjOllos that the trac-github plugin is the best way to accomplish the integration that you want. One of the main features of the plugin is that it supports "direct changeset TracLinks to GitHub's repository browser." Per the Trac site, TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system — such as changesets and commit messages. This sounds like the feature you are looking for to provide links from Trac to revisions in Git.
In version 2.3 of the plugin, it states that they have added "Support webhook signature verification for post commit hooks."
They also provide some nice setup steps which can sometime be lacking with other Trac plugins.
github only list top several issues I posted or commented, so I'm wondering how to search for the rest of them myself, of all issues that I myself participated.
I achieved this by putting is:issue involves:my-username in GitHub search.
This chapter from official docs can be really helpful GitHub Help: Searching issues and pull requests.
Converting my comment to an answer - once you're logged in, navigating to https://github.com/issues will show all your issues (categorized to open and closed ones).
There isn't an officially supported way to do that yet. See issue: https://github.com/isaacs/github/issues/283.
However, in the Notification Settings, there is an option called "Include your own updates" which is unchecked by default.
If you check that, Github will send you an email for every comment/PR you make. Now you can use appropriate email filters/labels to make sure it doesn't clutter your email. Then searching for the issue you commented reduces to a problem of searching your email, which if done correctly, is much efficient.