[Feature Request] Automatic export of Documents

[jnkue]

Description

I have created a PR #13722 to automatically export documents either manually or via workflow to the filesystem, a S3 bucket or SFTP sever.

In my opinion its a great feature and really adds important functionality.
Especially for German "GoDB" but also lot of other use cases.

Unfortunately my PR got automatically closed because of slop detection but I think it was a false positive here.

Related discussions:

GoBD:
#10379
#1880

S3:
#762

Document export:
#13615

For details please look at the PR #13722.
There is all the code and more explanation.

My main questions before I open a new PR would be:
Am I heading into the right direction ?
Do you have additional ideas how to improve this ?

P.S.:
In my opinion, the PR bot's failure threshold should be increased.
With a medium-sized PR like mine, you can get automatically closed very easily. I changed 52 files (limit: 50), had a 5,000-character description (limit: 2,500), and more than 10 comments. That already results in 3 failed checks.
Then even a small issue, like a missing heading or insufficient profile information, can lead to the PR being closed. I think the bot should be more forgiving for larger PRs.

Other

No response

[shamoon]

In my opinion, the PR bot's failure threshold should be increased.

No. We are not living in the same world we were even 1y ago. Pull requests used to be their own "CV". Opening a PR was a demonstration of the author's ability to reason, plan, and write code. Now it is nothing of the sort. We have no way to "tell" who threw a prompt into Claude vs who is an experienced dev, etc. Especially when that user has no meaningful paper trail on GitHub of OSS work or otherwise, let alone in Paperless-ngx.

By your own admission, you have very little experience with Angular development, so ask yourself would you have opened the PR like that in 2023, if Claude didnt do it for you? If not, why would we trust your "review" of its work? If you cant do that review, what are you bringing to the table besides the initial idea? If it's just an idea, post an idea, not a PR.

So the AI Slop bot is just fighting fire with fire. Sad, but the reality of this brave new world.

See #13722 (comment)

[stumpylog]

Dear lord. Opening 2 PRs like that, then this basically c&p of the PR bodies.

[amo13]

The feature makes a lot of sense to me.
But I am totally on your side when it comes to code quality and AI slop. Thank you @shamoon for sticking to the policies put in place to keep quality and stability as top priority!

[jnkue]

Hi
I am really sorry guys. I did not want to waste your time.

I just wanted to contribute a potential solution for the GoDB topic with additional benefit for all of the community and I think there is great interest for that.
You can also find a lot of discussion outside of GitHub (see links below).

@shamoon I brought more than the idea namely a potential concept of how to solve this: With a export action, export targets and a export record trace. This is why I opened a PR. I explicitly noted not to merge this. I just wanted some feedback.
This was my mistake and I should have just opened a discussion in the first place. Sorry!

I will close this discussion for now.

1
2
3
4
5

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.