deploy falsely claims no strains affected by remote repo

[rofe]

Description
When starting from scratch with a simple demo, following the getting-started.md, hlx deploy will claim that the remote repo won't affect any strains, even though the default strain will be.

To Reproduce
Steps to reproduce the behavior:

1. hlx demo mydemo
2. cd mydemo
3. git remote add origin https://github.com/myname/myproject.git
4. hlx up --save-config
   Your new helix-config.yaml will now look like this:

#
# helix configuration for local development
#
version: 1

definitions:
  defaults:
    - &localRepo "http://localhost/local/default.git"
    - &defaultRepo "https://github.com/myname/myproject.git"

strains:
  - name: dev
    url: http://localhost:3000/
    code: *localRepo
    content: *localRepo
    static: *localRepo

  - name: default
    code: *defaultRepo
    content: *defaultRepo
    static: *defaultRepo

5. hlx deploy --dirty
   Observe error output:

error: Remote repository https://github.com/myname/myproject.git#master does not affect any strains.
      
Add a strain definition to your config file:
name: fd3f9d80-8da1-4903-9c07-4565e73c1382
code: https://github.com/myname/myproject.git#master
content: https://github.com/myname/myproject.git
static: https://github.com/myname/myproject.git/htdocs

Alternatively you can auto-add one using the --add <name> option.
null

Expected behavior
hlx deploy should recognize that the default strain is affected, and deploy as expected.

Version:
v0.13.14

Additional context
The workaround is to manually append #master to the &defaultRepo variable in helix-config.yaml, then run hlx deploy again.

[tripodsan]

related to adobe/helix-shared#86

[tripodsan]

🎉 This issue has been resolved in version 0.14.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀