Conversation
|
@CharlieTLe did you open this? Why? No right? I guess the CI creates a PR in your name :D. We should probably address that @kd7lxl |
Due to the repo permissions, which I don't have access to, this is the best the admin would do. We have a slack thread about it |
CharlieTLe
force-pushed
the
release-3.2.1
branch
from
73389c3 to
7dee3d5
Compare
CharlieTLe
force-pushed
the
release-3.2.1
branch
from
7dee3d5 to
9be62e0
Compare
|
Can we close this? This doesn't do anything? We only did CI related commits in the meanwhile: v3.2.0...master |
It will continue to be updated with every commit until we feel it is worth merging, so I wouldn't close it. If you have some time you could update the job to ignore CI-only commits, but the edge cases around that lead me to just leave it like it is. |
CharlieTLe
force-pushed
the
release-3.2.1
branch
7 times, most recently
from
5b85411 to
1aa91ef
Compare
CharlieTLe
force-pushed
the
release-3.2.1
branch
2 times, most recently
from
2be05b4 to
9c49190
Compare
Signed-off-by: kd7lxl <kd7lxl@users.noreply.github.com>
CharlieTLe
force-pushed
the
release-3.2.1
branch
from
9c49190 to
31d3f32
Compare
Signed-off-by: Tom Hayward <thayward@infoblox.com>
3 participants
Automated release PR for version 3.2.1