linksplatform / linksplatform/RegularExpressions.Transformer.HasuraSQLSimplifier
Reenable NuGet publishing to GitHub NuGet registry.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```YAML
pushCSharpNuGetToGitHubPackageRegistry:
needs: testAndDeploy
if: github.event_name == 'push'
runs-on: windows-latest
steps:
- uses: actions/checkout@v1
with:
submodules: true
- uses: nuget/setup-nuget@v1
- name: Publish CSharp NuGet to GitHub Package Registry
run: |
dotnet build -c Release
dotnet pack -c Release
nuget source Add -Name "GitHub" -Source "https://nuget.pkg.github.com/linksplatform/index.json" -UserName linksplatform -Password ${{ secrets.GITHUB_TOKEN }}
nuget push **/*.nupkg -Source "GitHub" -SkipDuplicate
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find the GitHub Actions workflow containing the pushCSharpNuGetToGitHubPackageRegistry job and compare it with the YAML in the issue. Check the workflow's push conditions and package-publishing steps; it is done when a push can publish the C# NuGet package to the GitHub NuGet registry without breaking the existing testAndDeploy dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100