Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Trouble publishing to other repo

See original GitHub issue

Describe the Issue

I’m trying to publish from MyOrg/MyRepo to MyOrg/myorg.github.io and can not get it to work. Publishing to a local gh-pages branch worked fine, but you can’t use a gh-pages branch for an org website.

Logs

##[debug]Evaluating condition for step: 'Deploy 🚀'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Deploy 🚀
##[debug]Loading inputs
##[debug]Evaluating: secrets.SEAN_DEPLOYMENT_PAT
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'SEAN_DEPLOYMENT_PAT'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Loading env
Run JamesIves/github-pages-deploy-action@releases/v3
Checking configuration and starting deployment… 🚦
Deploying using Access Token… 🔑
Configuring git…
/usr/bin/git init
Reinitialized existing Git repository in /home/runner/work/TorqIT-next/TorqIT-next/.git/
/usr/bin/git config user.name IronSean
/usr/bin/git config user.email seanrmackay@gmail.com
/usr/bin/git remote rm origin
/usr/bin/git remote add origin ***github.com/TorqIT/torqit.github.io.git
/usr/bin/git fetch
remote: Repository not found.

Additional Comments

Here is my workflow

name: Node.js CI

on:
  push:
    branches: [ master ]
#   pull_request:
#     branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [12.x]

    steps:
    - uses: actions/checkout@v2
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
    - run: npm ci
    - run: npm run build --if-present
    - run: npm test
    - run: npm run export
      env:
        CI: true
    - name: Deploy 🚀
      uses: JamesIves/github-pages-deploy-action@releases/v3
      with:
        ACCESS_TOKEN: ${{ secrets.SEAN_DEPLOYMENT_PAT }}
        REPOSITORY_NAME: TorqIT/torqit.github.io
        BRANCH: master # The branch the action should deploy to.
        FOLDER: out # The folder the action should deploy.

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

IronSeancommented, Apr 9, 2020

That did it!

I skimmed the first two thirds of the example assuming they were generic checkout and build steps and didn’t read that comment. Thank you for your help!

Now I just need to inject a .nojeckyll file and I think I’m in business.

0reactions

JamesIvescommented, Apr 9, 2020

You should be able to commit that directly to the branch, the history will remain in tact so it won’t need to be written every time you make a push.

Glad it worked!

Top Results From Across the Web

Transferring an issue to another repository - GitHub Docs

On GitHub.com, navigate to the main page of the repository. · Under your repository name, click Issues. · In the list of issues,...

How to publish a Git repository - ImageJ Wiki

Repositories · 1. initialize a bare repository on becherovka · 2. Register that repository as a remote repository on your laptop by issuing...

I cannot publish my VS Code repository to GitHUB

This is usually caused by another repository pushing hint: to the same ref. You may want to first integrate the remote changes hint:...

An Introduction to Collaborating with Version Control

Publishing Your Repository to GitHub ... the basics of creating a repository and making commits, let's talk about how to share your work...

Publishing an existing project to new remote repository not ...

Page: https://docs.microsoft.com/en-us/visualstudio/mac/set-up-git-repository#publishing-an-existing-project. Error: “Version control operation failed:”.