Skip to content

Add exclude flag and skip the devocntainer for bink and bootc-operator #222

Merged
jeckersb merged 4 commits into
bootc-dev:mainfrom
alicefr:skip-repo
Jul 6, 2026
Merged

Add exclude flag and skip the devocntainer for bink and bootc-operator #222
jeckersb merged 4 commits into
bootc-dev:mainfrom
alicefr:skip-repo

Conversation

@alicefr

@alicefr alicefr commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

For bootc-operator and bink, we don't relay on devcontainer, so we would like to skip the sync of the devcontainer directory

alicefr added 4 commits July 6, 2026 16:56
Introduce the exclude flag to skip certain directories and files. This
use clap in order to have a better parsing of the flags, the exclude can
be repeated multiple times.

Assisted-by: AI
Signed-off-by: Alice Frosi <afrosi@redhat.com>
Automatic update of dependencies in Cargo.lock.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
Test if the exclude directory and the skip.txt aren't included in the
final synchronization-

Assisted-by: AI
Signed-off-by: Alice Frosi <afrosi@redhat.com>
For bootc-operator and bink, we aren't use devcontainers, hence we skip
the synchronization of these files.

Assisted-by: AI
Signed-off-by: Alice Frosi <afrosi@redhat.com>
let current_commit = &args[3];

CommonFileSyncer::sync(&infra_path, &target_path, current_commit)?;
CommonFileSyncer::sync(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a blocker but this is getting to the point we should probably break these into a struct SyncOpts or whatnot, I think the ergonomics are clearer as opposed to growing the args and needing to keep track of the ordering of parameters.

@jeckersb jeckersb merged commit 9b0d23f into bootc-dev:main Jul 6, 2026
3 checks passed
@cgwalters

Copy link
Copy Markdown
Contributor

But...they are more likely to make things work if e.g. someone launches in Codespaces for these repos.

#100 is tracking actually using devcontainers more in GHA flows, which I think still makes sense.

Is it really worth carrying a divergence here?

@alicefr

alicefr commented Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

But...they are more likely to make things work if e.g. someone launches in Codespaces for these repos.

#100 is tracking actually using devcontainers more in GHA flows, which I think still makes sense.

Is it really worth carrying a divergence here?

Well, we need to test it that's the main reason why we disable it. Right now, we deliver bink as container image but we should try to deploy it with devcontainer. The bootc-operator strongly relay on bink, so once it is on board we can re-enable it.

@alicefr

alicefr commented Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

Filed bootc-dev/bink#95

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants