Skip to content

Revit 2026#237

Draft
djsiroky wants to merge 7 commits into
masterfrom
revit-2026
Draft

Revit 2026#237
djsiroky wants to merge 7 commits into
masterfrom
revit-2026

Conversation

@djsiroky
Copy link
Copy Markdown
Member

Description

Tasks

  • Submitted PR
  • Published to BIM Staging
  • Tested by David
  • Published to BIM Master

@djsiroky djsiroky marked this pull request as ready for review September 24, 2025 18:50
@djsiroky djsiroky marked this pull request as draft September 24, 2025 18:50
I have also added accompanying documentation on how to utilize the script and how it works in implementation_plan.md and walkthrough.md
@MohsenHOK64
Copy link
Copy Markdown
Contributor

I have added the GitHub workflow file for building the HOK Revit Addins via GitHub Actions. It triggers a build and creates a release whenever there is a push or pull request merge to the "main" branch, but the script needs to be adjusted for this by adding "main" on line 7 and 9.

The repo also needs to have the following secrets added via Settings > Secrets and Variables > Actions > Repository Secrets:

  • CODE_SIGNING_CERT: CISign.pfx certificate file encoded as Base64. To create this, run the following command on the .pfx certificate file in PowerShell and paste it as the value for this secret:

    • [Convert]::ToBase64String([IO.File]::ReadAllBytes("path\to\CISign.pfx")) | Set-Clipboard
  • CERT_SIGNING_PASS: The password for the .pfx certificate file stored as plaintext. Enter the password in the value of this secret as-is.

  • NUGET_FEED_URL: The source nuget package for our quick-fix for RestSharp, just adds the HOK_RestSharp package to prevent addin dependancy errors. The value for this secret is the following link:

  • NUGET_PAT: The Personal Access Token from Azure DevOps with "Packaging (read)" scope. To generate:

    1.      Go to dev.azure.com → your organization
    2.      Click your avatar (top right) → Personal access tokens
    3.      Click New Token
    4.      Set a name (e.g. GitHub Actions NuGet Read)
    5.      Under Scopes, select Packaging → Read
    6.      Click Create and copy the token
    7.      Paste it as the secret value in GitHub
    
  • SETTINGS_JSON: HOK-Specific addin settings (Settings.json). Please reach out to Dan Siroky for information about this file. The value of this secret should be set by running the following PowerShell command and pasting the contents into the value for this secret:

    • [Convert]::ToBase64String([IO.File]::ReadAllBytes("path\to\your\Settings.json")) | Set-Clipboard

@MohsenHOK64
Copy link
Copy Markdown
Contributor

One thing to note for the CISign.pfx file:

I created a certificate with my user profile but since I am leaving HOK, this certificate will need to be regenerated, or use the old certificate file that was used in the previous version of the build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants