Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

File markings not taken into account in import #787

Closed
SamuelHassine opened this issue Nov 15, 2024 · 0 comments
Closed

File markings not taken into account in import #787

SamuelHassine opened this issue Nov 15, 2024 · 0 comments
Assignees
@SamuelHassine
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.3.12

Comments

@SamuelHassine
Copy link
Member

Description

File markings not taken into account in import
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Nov 15, 2024
@SamuelHassine SamuelHassine added this to the Release 6.3.12 milestone Nov 15, 2024
@SamuelHassine SamuelHassine self-assigned this Nov 15, 2024
SamuelHassine added a commit that referenced this issue Nov 15, 2024
@SamuelHassine
[client] Take into account marking on files at import (#787)
f042c8c
@SamuelHassine SamuelHassine mentioned this issue Nov 15, 2024
Merged
SamuelHassine added a commit that referenced this issue Nov 15, 2024
@SamuelHassine
[client] Take into account marking on files at import (#787)
cb71925
SamuelHassine added a commit that referenced this issue Nov 15, 2024
@SamuelHassine
[client] Take into account marking on files at import (#787)
f00e104
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.3.12
Development

No branches or pull requests
1 participant
@SamuelHassine