Rename to helix-pipeline?

[trieloff]

Given that all Helix-related repos follow the helix-* naming pattern, it might be time to rename this to helix-pipeline.

I'm a bit sad to see the name "Hypermedia" go, but it's still in the helix acronym:

Hypermedia Experience Language Intelligizer & eXpressifier

[tripodsan]

+1

[rofe]

+1 i was thinking the same thing

[stefan-guggisberg]

+1

[trieloff]

@kptdobe can you take a look at the failing smoke test: https://circleci.com/gh/adobe/helix-pipeline/650 the error message looks very un-pipelineish to me.

[trieloff]

@sjvs we have renamed another repository https://github.com/adobe/hypermedia-pipeline/ to https://github.com/adobe/helix-pipeline/ and would like to update LGTM, too.

[kptdobe]

Well, the error message is a known one: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

[kptdobe]

Error is being treated in adobe/helix-cli#353
In the meantime, we applied a tmp fix which unlocked the CI.
But the smoke tests are still red with now a pipelineish error: https://circleci.com/gh/adobe/helix-continuous/71
Something wrong again with the include of the nav...

[tripodsan]

released on npm:

https://github.com/adobe/helix-pipeline/releases/tag/v0.9.0
https://www.npmjs.com/package/@adobe/helix-pipeline/v/0.9.0

[sj]

@trieloff: LGTM should now automatically pick up on GitHub repository renames. Let me know if that's not the case!

[trieloff]

@sjvs yes, it did. Just noticed it while enabling LGTM for https://github.com/adobe/project-helix.io (where I'm going to test the new query)