I am currently trying to use the CLA-Assistant-Lite github action.
The workflow appears to have an issue related to the use of Node.js 12.
Someone has opened a pull request to address the issue that I would like to use.
I can not figure out how to modify my .yml to use the code from the pull request vs. the current release.
The .yml currently has the line :
uses: contributor-assistant/github-action#v2.2.1
How can I modify it to use the pull request code instead of the v2.2.1 tag?
You can change the uses line to reference the SHA from the commit you want to use instead of a version. It also accepts a branch. Simply change the part after the # symbol.
In your case I think you want:
uses: contributor-assistant/github-action#4b65b2db8e3217d589ae15875814a011c1a9b69d
See the actions docs here about syntax for uses
Related
Does anyone know what this does ?
uses: ./
I see it used in quite a few places but cannot seem to find any reference for it.
The uses keyword of github actions is used to specify the action that should be executed as part of a workflow. The ./ value tells GitHub to use the action defined in the current repository, rather than referencing a pre-built action.
It's also possible to specify the path to the action within the repository, rather than using ./. For example:
steps:
- uses: ./path
with:
parameter1: value1
parameter2: value2
This would execute the action located at ./path within the repository.
I see the documentation in github actions to run a powershell script in a step. I need to increment version number and checkin versions.txt file in GitHub Actions using powershell. Can I accomplish this by running a powershell script from my folder and by using git.exe and powershell commands?
How do I set a variable from powershell script to use the version number in subsequent steps?
So there are two questions in your question, I will answer in reverse order.
To have one step (for example shell script) set a value for subsequent steps, you can use the special workflow commands which are just done by outputting specially formatted strings to STDOUT.
In your case, are looking for Setting an Output Parameter:
echo "::set-output name=version::1.2.3"
Which can then be read by subsequent steps, like this (for example):
env:
VERSION: ${{ steps.the-other-step-id.outputs.version }}
As for having GitHub actions modify code and then check it in, I would strongly advise against it as it will a) complicate your workflow, b) might create "workflow loops", where actions-originated checkins trigger this/other workflows.
For version tagging, I suggest you use tags as it is the almost universally accepted way to mark versions in source control. You might want to have a local script that both tags and updates your version.txt, and then your workflow just reads the file or the tag.
I have two Jenkins instances running. An old (legacy) one at version 1.614 and a new one with 1.633.
In the old one it is possible to use HTML in the job description (it even does syntax highlighting editing it). The new one doesn't. HTML content is escaped and shown as plain text. I could not find a change in the release notes explaining this behavior. Is there a configuration that I'm missing?
In the Global security menu:
Select this value to display HTML:
For enabling it via config: you have to install the configuration as code (CASC) plugin (https://plugins.jenkins.io/configuration-as-code/) , and add the following entries to your config file(s - I guess, it is better to have multiple files for a better overview):
markupFormatter:
rawHtml:
disableSyntaxHighLighting: false
If you don't need highlighting, change it to true
I am trying to integrate clearcase with Hudson, but auto build is not triggering while merge or checkout.
Created dynamic view "sundaa4_Hudson_Test" and gave the config spec which I used in clearcase
When I gave manual build its showing error
Workspace is not creating in path .hudson\jobs\Hudson_Testing_Sijith\workspace
PLease give some input on this
Make sure your config spec ends with a selection rule like:
element * /main/LATEST
Or it won't select much, which would explain why Hudson doesn't create anything (it doesn't detect any change).
A cleartool lsview which returns a line starting with '*' means the dynamic view is already started: no need to repeat multiple cleartool startview.
Make sure your View root does exists: usually, the MVFS drive for dynamic view is M:\, not K:\.
I'm a complete noob at Mercurial API and Python, but I'm trying to write a useful extension for myself and my colleagues now.
Let's assume I have a repository which contains some code and an auxiliary file .hgdata. The code and .hgdata are both under Mercurial's control. When I execute a command pull-extended which is provided by my extension, I want it to make a pull and then to analyze the state of a .hgdata and probably make some additional actions. The problem is that when my command is invoked, it just pulls the incoming changesets, but it can't look into the actual .hgdata without making a preceding repository update. Is there any way to watch the after update .hgdata besides repository update?
I've received an answer on the Mercurial's official IRC channel:
In order to get an actual file state after making a pull, we may use repo[revision][file].data().
P.S. I haven't checked that yet. If it works, I will close the question.