Skip to content

Conversation

@josephjclark
Copy link
Collaborator

Fixes #1219

This basically flips the merge command.

Right now its merge source, which pulls the source project into what's checked out.

This PR makes it merge target, which pushes the local project into whichever you want.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our Responsible AI Policy

josephjclark and others added 7 commits January 8, 2026 13:50
* runtime: support first-class start key

* drop requirement for top level workflow key

* project: refactor support for the start key

* fix tests

* fix an issue where input path isn't parsed correctly

* cli: suppress adaptor warning when running a yaml file

* new tests for running yaml files

* fix more tests

* handle options on a non-nested workflow yaml
* allow workflow to be executed directly through workspace

* types

* remove default job.js

* changeset

* integration test

* another integration test

* support credentials on workspace config

* remove mock

* project: better handling of start in workflow.yaml

* apply credentials map

* add integration test for execute + credetial map

* fix test

* remove unused test

* format

* go deep on input tests

* throw if workflow not found

* project: fix an issue loading alias for a v1 project

* update v1 integration test

* fix integration test

* better credential map handling

* fix test

It was secretly failing all along

* ensure collections and credential map can both be set

* changesets

* test tweak

* more integration test tweaks

* fix integration tests yet again

Turns out test order is important, so it was passing with .only but failing en masse

* change  v2 test order

* let -> const

* update v2 test

configuration uuids as numbers break things

* yet another test fix
@github-project-automation github-project-automation bot moved this to New Issues in v2 Jan 13, 2026
@josephjclark
Copy link
Collaborator Author

merge only updates the workign tree right? It doesn't push the project file or anything,. So if I'm on staging, and I do merge main, the checked out branch is still taging - but the contents are staging + main. Which is kinda wierd.

That's why pulling into your branch felt better.

But you're in a wierd no-man's land because after merge, your local file system has sort of diverged from all remote targets, until you push.

Will have to come back to this with a fresh mind tomorrow

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

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

I'm sure the CLI merge API is wrong :(

2 participants