It seems you might be experiencing issues with the GitHub Actions not triggering after deploying your project to GitHub Pages. Here are a few things to check:
Deployment Component: Ensure you’ve added the DeployToGithubPages component to your scene correctly. You must provide a valid GitHub repository URL here.
Valid URL: Double-check that the URL you pasted in the repositoryUrl field follows the correct format, which should look like https://github.com/username/repo-name.git. If it is a GitHub Pages URL, ensure it’s in the proper format too (see deployment) (see the documentation).
GitHub Actions Setup: Ensure that you have a .github/workflows/ directory in your repository with a YAML file defining your workflow. If it’s missing, the action won’t trigger.
Permissions: Check the repository’s settings to ensure Actions are enabled. Sometimes, Actions can be restricted in organizational repositories.
Logs: If the actions still aren’t firing, review the repository’s “Actions” tab for any logs or error messages.
Unity Version: Ensure you are using a compatible version of Unity that supports the Needle Engine’s deployment features, particularly the DeployToGithubPages component.
You may also consider re-running the workflow manually to check for any immediate errors.
If you continue to experience issues, please provide additional details such as your Unity version and if you have any specific errors in the Actions tab.
For further information, you can check the deployment section in the official documentation (see deployment).
Let me know how it goes or if you need further assistance!
1 replies left - Get a PRO license for more AI replies. thread_jtD8FHoD2CuWv9GmYAxJWX7L Reply to this message to continue the conversation
Hi, ive tried to reproduce it but it worked for me here (just created a new empty repo and deployed to it)
Which Nodejs version are you using? Did you see any error in the Unity console? The upload itself looks correct. Can you just try to deploy again? Maybe there was an issue on github’s site?
Build Production build succeeded in 68,5 sec: E:\OneDrive\00-Game Design\04-Unity\POC_NeedleThirdy\Library\Needle\Sample/dist
By Type:
• .html → x 1 = 0,0 mb
• .json → x 5 = 0,2 mb
• .png → x 4 = 0,5 mb
• .glb → x 40 = 2,9 mb
• .ico → x 1 = 0,0 mb
• .js → x 15 = 4,3 mb
• .css → x 1 = 0,0 mb
• .svg → x 1 = 0,0 mb
• .jpg → x 1 = 0,0 mb
• .webp → x 2 = 0,0 mb
• .wasm → x 2 = 0,7 mb
• Total = 8,6 mb
----
By Directory:
• dist → x 2 = 0,0 mb
• assets → x 59 = 6,9 mb
• include → x 12 = 1,8 mb
UnityEngine.Debug:Log (object)
Needle.Engine.MenuItems/<InternalExportAndBuildTask>d__34:MoveNext () (at ./Library/PackageCache/com.needle.engine-exporter@3.51.4/Core/Editor/Actions/MenuItems.cs:424)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1<bool>:SetResult (bool)
Needle.Engine.ActionsBuild/<InternalBuildDistTask>d__3:MoveNext () (at ./Library/PackageCache/com.needle.engine-exporter@3.51.4/Core/Editor/Actions/ActionsBuild.cs:106)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1<bool>:SetResult (bool)
Needle.Engine.Utils.ProcessHelper/<RunCommand>d__6:MoveNext () (at ./Library/PackageCache/com.needle.engine-exporter@3.51.4/Common/Runtime/Utils/ProcessHelper.cs:128)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1<Needle.Engine.Utils.ProcessHelper/RunResult>:SetResult (Needle.Engine.Utils.ProcessHelper/RunResult)
Needle.Engine.Utils.ProcessHelper/<RunCommand>d__7:MoveNext () (at ./Library/PackageCache/com.needle.engine-exporter@3.51.4/Common/Runtime/Utils/ProcessHelper.cs:331)
UnityEngine.UnitySynchronizationContext:ExecuteTasks ()
I’ve tried to Build & Deploy, the only Deploy today (and a lot yesterday) but it’s not working.
No action or workflow is launched at the end on Github
I tried forking your repo and publishing to my fork, that worked as well. I guess your settings aren’t forked tho - let’s see if your logs contain any info when you’ve sent the report