New git commits don't mark pull step dirty
Bug #1704103 reported by
Michał Sawicz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Triaged
|
Low
|
Leo Arias | ||
Bug Description
Given a part:
foo:
plugin: dump
source: .
source-type: git
$ snapcraft
Preparing to pull foo
Pulling foo
Preparing to build foo
Building foo
Staging foo
Priming foo
[...]
$ git commit -m test --unchanged
$ snapcraft
Skipping pull foo (already ran)
[...]
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| importance: | Undecided → Low |
| assignee: | nobody → Leo Arias (elopio) |
| status: | New → Triaged |
To post a comment you must log in.
We agreed that we would treat these parts as dependencies, just as new stage-packages don't mark the build dirty either and we would focus on `source-type: local` first.